https://forge.ispras.ru/https://forge.ispras.ru/favicon.ico?16490126692020-08-14T19:11:56ZOpen-Source ProjectsKlever - Feature #10461: Support verification of Linux kernel modules on the ARM architecturehttps://forge.ispras.ru/issues/10461?journal_id=394962020-08-14T19:11:56ZEvgeny Novikovnovikov@ispras.ru
<ul></ul><p>I expect 3 components of Klever needs to be adjusted to meet a non-standard architecture. They are CIF, CIL and a verifier (at the moment just CPAchecker). I hope that at least for CIL and CPAchecker nothing except some (maybe just one) option will be necessary. As for CIF, cross CIF should be used. Anyway, I do not expect many differences between various architectures. Moreover, we can take into account different aspects of particular projects by describing architecture adjustments separately for all supported project if they need this at all.</p>
<p>That's why I suggest to include a new file called <em>architecture.json</em> which will incorporate all specific stuff corresponding to different architectures into verification jobs and allow users to select one of described architectures within <em>job.json</em>.</p>
<p>If somebody has any objections it would be great to hear them here soon before I will implement the suggested approach.</p> Klever - Feature #10461: Support verification of Linux kernel modules on the ARM architecturehttps://forge.ispras.ru/issues/10461?journal_id=395112020-08-21T14:09:44ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>I did the job in branch <em>arm-support</em>. I did not implement a job specific architecture description because we do not support appropriate projects for testing. So, architecture specific configuration is global for all now, but it will be quite easy to change this in future if necessary.</p>
<p>Besides, CIL does not support ARM specific processing (<a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Feature: Support ARM architecture (Closed)" href="https://forge.ispras.ru/issues/10471">#10471</a>), but it does not seem that this cause considerable issues.</p>
<p>If one would like to verify Linux kernel modules on ARM, one should get cross CIF (<a class="wiki-page new" href="https://forge.ispras.ru/projects/klever/wiki/How_to_get_cross_CIF_for_building_and_verification_of_Linux_kernel_loadable_modules_on_ARM">How to get cross CIF for building and verification of Linux kernel loadable modules on ARM</a>), prepare an appropriate build base and specify "architecture": "ARM" within <em>job.json</em>.</p> Klever - Feature #10461: Support verification of Linux kernel modules on the ARM architecturehttps://forge.ispras.ru/issues/10461?journal_id=395132020-08-21T14:55:20ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul><p>Tests passed, so, I merged the branch to master in <a class="changeset" title="Update Clade" href="https://forge.ispras.ru/projects/klever/repository/331/revisions/e6a028d78e31e480f5da73d4fcfffc881482931d">e6a028d78</a>.</p>