[ http://tools.oasis-open.org/issues/browse/VIRTIO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Tsirkin updated VIRTIO-30:
----------------------------------
Description:
in the past we sometimes wanted an ability to make driver gracefully fail early in initialization
if it does not recognize/support a feature.
One such example we are introducing right now is the new VERSION_1 feature.
Drivers need to be able to add buffers before initialization is complete.
We also need a "lock point" after which drivers do not change features.
was:
in the past we sometimes wanted an ability to make driver gracefully fail early in initialization
if it does not recognize/support a feature.
One such example we are introducing right now is the new VERSION_1 feature.
Drivers need to be able to add buffers before initialization is complete.
We also need a "lock point" after which drivers do not change features.
Proposal: http://markmail.org/search/?q=subject%3A%22%5BPATCH%20v2%5D%20initialization%3A%20add%20extra%20device%20status%20handshake%22+list%3A%22org.oasis-open.lists.virtio%22 (was: 1. require a driver to first ack all features it recognizes (linux does this already)
2. require driver to check status afterwards
3. add new device_ok status)
> extend initialization sequence
> ------------------------------
>
> Key: VIRTIO-30
> URL: http://tools.oasis-open.org/issues/browse/VIRTIO-30
> Project: OASIS Virtual I/O Device (VIRTIO) TC
> Issue Type: New Feature
> Environment: guest driver
> Reporter: Michael Tsirkin
> Assignee: Michael Tsirkin
>
> in the past we sometimes wanted an ability to make driver gracefully fail early in initialization
> if it does not recognize/support a feature.
> One such example we are introducing right now is the new VERSION_1 feature.
> Drivers need to be able to add buffers before initialization is complete.
> We also need a "lock point" after which drivers do not change features.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
