Abstract: This disclosure concerns the co-design of a testbench (100) and driver (102) of a device. It is an advantage in at least some embodiments that it improves driver reliability and reduces development cost. It does this by re-using the device functional layer (70) that is dependent on the device class but independent of the specific device and specific operating system (OS) of the driver. The device functional layer (70) is re-used as it is implemented in the device's testbench (100) and also as the core part of the device (driver (102). A scenario layer (68) is also used that is able to test the generic device interface (72) and device functional layer (70) in the testbench (100) environment, and the testing includes testing for responses to OS requests. This helps provide more exhaustive testing.

Abstract: The invention concerns reliable writing of database log data, In particular, the invention concerns a computer system, methods and software to enable database log data to be written to recoverable storage in a reliable way. There is provided a computer system (100) for writing database log data to recoverable storage (60) comprising a durable database management system (DBMS) (40); and a hypervisor (80) or kernel 81 that enables communications between the recoverable storage device driver (52) and a recoverable storage device (60) to write the log data written to the non recoverable storage (92) and (42) to the recoverable storage device (60) asynchronously to the continued writing of log data to the non-recoverable storage (42) and (92). This allows the DBMS (40) to ensure recoverability and serializability and still allowing logs to be written asynchronously removing a performance bottleneck for the DBMS.

Abstract: This disclosure concerns the co-design of a testbench (100) and driver (102) of a device. It is an advantage in at least some embodiments that it improves driver reliability and reduces development cost. It does this by re-using the device functional layer (70) that is dependent on the device class but independent of the specific device and specific operating system (OS) of the driver. The device functional layer (70) is re-used as it is implemented in the device's testbench (100) and also as the core part of the device (driver (102). A scenario layer (68) is also used that is able to test the generic device interface (72) and device functional layer (70) in the testbench (100) environment, and the testing includes testing for responses to OS requests. This helps provide more exhaustive testing.