Abstract | ||
---|---|---|
Faulty device drivers are a major source of operating system failures. We argue that the underlying cause of many driver faults is the separation of two highly-related tasks: device verification and driver development. These two tasks have a lot in common, and result in software that is conceptually and functionally similar, yet kept totally separate. The result is a particularly bad case of duplication of effort: the verification code is correct, but is discarded after the device has been manufactured; the driver code is inferior, but used in actual device operation. We claim that the two tasks, and the software they produce, can and should be unified, and this will result in drastic improvement of device-driver quality and reduction in the development cost and time to market. In this paper we discuss technical issues involved in achieving such unification and present our solutions to these issues. We report the results of a case study that applies this approach to implement a driver for an Ethernet controller device. |
Year | Venue | Keywords |
---|---|---|
2010 | HotDep | verification reuse,faulty device driver,actual device operation,driver fault,driver development,driver code,bad case,device verification,improved device driver reliability,development cost,ethernet controller device,case study |
Field | DocType | Citations |
Control theory,Reuse,Computer science,Unification,Ethernet,Software,Time to market,Embedded system,Distributed computing | Conference | 1 |
PageRank | References | Authors |
0.35 | 10 | 6 |
Name | Order | Citations | PageRank |
---|---|---|---|
Leonid Ryzhyk | 1 | 212 | 16.05 |
John Keys | 2 | 8 | 1.86 |
Balachandra Mirla | 3 | 5 | 0.76 |
Arun Raghunath | 4 | 17 | 2.51 |
Mona Vij | 5 | 36 | 4.51 |
Gernot Heiser | 6 | 2525 | 137.42 |