summaryrefslogtreecommitdiff
path: root/fix-numbers.pl
diff options
context:
space:
mode:
authorrusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2013-09-03 00:55:29 +0000
committerrusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2013-09-03 00:55:29 +0000
commit9ef9ca824beaa2069c7a02982daf7bc2ab72124e (patch)
tree2d3015ab62a568b78e4f01a1019d2e94615791ea /fix-numbers.pl
parent7c748b4a83c2d02bcedfd2670821bac3fb9cbec9 (diff)
2.5.6.6.3: add configuration change event
This adds an event for changes to LUN parameters, for example capacity. These are reported in virtio-blk via configuration changes, and we want a similar functionality in virtio-scsi too. There is no list of supported parameter changes, instead we just refer to the list of sense codes in the SCSI specification. This event will usually be serviced in one of three ways: 1) call an OS service to revalidate the disk, either always or only for some specific sense codes; 2) somehow pass the sense directly to the upper-level driver; 3) inject a TEST UNIT READY command into the upper-level device, so that the OS will see the unit attention code and react. Of course a mix of the three is also possible, depending on how the driver writer prefers to have his layering violations served. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> See: https://lists.oasis-open.org/archives/virtio-comment/201308/msg00032.html Signed-off-by: Rusty Russell <rusty@au1.ibm.com> git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@30 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
Diffstat (limited to 'fix-numbers.pl')
0 files changed, 0 insertions, 0 deletions