Linux Driver Verification

h1. Benchmarking C Software Verifiers With LDV Tools

The core component of Linux Driver Verification tools is verification tool for C language.  Static analysis of driver sources with instrumented environment models and rules are eventually passed to such a verifier, which performs the most important part of the whole work.

No wonder that the speed and quality of the overall analysis heavily depends on how well and fast the verifier performs.  But the best verifier is yet to find!  There are several static C verifiers, which perform differently, and without experimenting it''s not clear which one is the best for our purpose.  Moreover, verifiers usually contain a number of tweaks and configuration opportunities, which should also be explored.  

So one of the goals of LDV program is to build a framework that aids us in answering such questions, as:

* Which configuration of a verifier works faster on a test driver set?

* Which verifier checks more drivers within a given time limit?

* How would it affect verification, if we supply verifier with more memory?

We developed special components that gather, analyze, visualize and compare statistics of verification of a lot of different drivers.  The drivers can either be automatically fetched from a pre-assembled test set, or could be automatically extracted from the Linux Kernel.

h2. Visualization and comparison

Here''s a sample experiment.  We used a test set with some "interesting" drivers (fixed and unfixed versions of those, in which we used to find bugs), which is included in default shipment of LDV tools (it''s called @generic@) to run "CPAchecker":http://cpachecker.sosy-lab.org/ with different time limits.  Here are the results

!http://forge.ispras.ru/attachments/518/bench1.png!

From this table we could see that (actually, this table doesn''t show us anything interesting.  I''ll re-run tests with different configurations and re-create the table to demonstrate that results can be useful).

Now let''s see how many degradations or improvements were there.  First, select some test runs to compare (hitting radio button near the "basis"):

!http://forge.ispras.ru/attachments/519/bench2.png!

And press the "Compare tasks" button to get to the comparison page:

!http://forge.ispras.ru/attachments/520/bench3.png!

Here we can see that our "basis" configuration dominates all others.  Indeed, some of the drivers that were detected as Safe or Unsafe in the "basis" configuration are not detected anymore, and are "Unknown" for other configurations we selected.

h2. How to use LDV for benchmarking

To use this benchmarking system you should first "download sources":/projects/ldv/wiki/Downloading_and_Building_LDV of LDV tools (we recommend downloading the master branch).  After downloading we recommend you to refer to file @VerifierDevelopersHowTo@ (see source:VerifierDevelopersHowTo).  It will tell you how you should install and use LDV tools in order to specifically address benchmarking verification tools.

Currently, only BLAST and CPAchecker verifiers are supported.  However, developing a convenient way to plug in other verifiers is on our roadmap.