Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
16
0

Year Published

2012
2012
2020
2020

Publication Types

Select...
2
2

Relationship

0
4

Authors

Journals

citations
Cited by 32 publications
(16 citation statements)
references
References 15 publications
0
16
0
Order By: Relevance
“…Linux Driver Verification (LDV) [7] is a program based on static analysis, which includes two adjacent lines of activity: 1) creation of a repository of potential faults and errors that may occur in Linux device driver, and 2) development and improvement of special-purpose verification tools for automatic detection of all errors specified in the repository. This project can be viewed at [8].…”
Section: IImentioning
confidence: 99%
“…Linux Driver Verification (LDV) [7] is a program based on static analysis, which includes two adjacent lines of activity: 1) creation of a repository of potential faults and errors that may occur in Linux device driver, and 2) development and improvement of special-purpose verification tools for automatic detection of all errors specified in the repository. This project can be viewed at [8].…”
Section: IImentioning
confidence: 99%
“…The characteristics of systems software, in particular kernel device drivers, might be similar and could have an impact on the validity of our experiments, but (Linux) driver verification is important enough to be representative on its own [15]. The Linux Driver Verification program of the Linux Verification Center [29] and Microsoft's Static Driver Verifier project [2] dedicate considerable resources to driver verification.…”
Section: Differences Between Verification-task Revisionsmentioning
confidence: 99%
“…on industrial code, in order to show the significant impact of precision reuse on regression verification (in terms of performance gains and increased number of solvable verification tasks). The benchmark verification tasks were extracted from the Linux kernel, which is an important application domain [15], and prepared for verification using the Linux Driver Verification toolkit (LDV) [29,31]. Our study consisted of a total of 16 772 verification runs for 4 193 verification tasks, composed from a total of 1 119 revisions (spanning more than 5 years) of 62 Linux drivers from the Linux kernel repository.…”
Section: Introductionmentioning
confidence: 99%
“…But the development community is increasingly looking for automatic techniques for verifying crucial properties, and the verification community is using Linux drivers as application domain for new analysis techniques. During the last years, three verification environments were build in order to define verification tasks from Linux drivers: the Linux Driver Verification project 1 [23], the Avinux project [27], and the DDVerify project 2 [32]. The Linux code base is a popular source for verification tasks [17,22,24,25].…”
Section: Overviewmentioning
confidence: 99%