← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] Commented: (VIRTIO-30) extend initialization sequence

From
OASIS Issues Tracker <>
Date
2013-10-03T05:09:45+00:00
ID
1975788490.19131380777039992.JavaMail.tomcat@customer-jira
Thread
[OASIS Issue Tracker] Commented: (VIRTIO-30) extend initialization sequence
[ http://tools.oasis-open.org/issues/browse/VIRTIO-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35074#action_35074 ] 

Rusty Russell commented on VIRTIO-30:
-------------------------------------

OK, rework appears here:
https://lists.oasis-open.org/archives/virtio/201310/msg00014.html

It adds FEATURES_OK, and requires driver to set DEVICE_OK before any use.

> 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 &quot;lock point&quot; 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
← Prev in month ← Prev in thread
Next in thread → Next in month →