OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Created: (VIRTIO-38) New status bit FEATURES_OK

New status bit FEATURES_OK

                 Key: VIRTIO-38
                 URL: http://tools.oasis-open.org/issues/browse/VIRTIO-38
             Project: OASIS Virtual I/O Device (VIRTIO) TC
          Issue Type: Bug
            Reporter: Rusty Russell

The current spec states :

2.2.1. Device Initialization

1. Reset the device. This is not required on initial start up.

2. The ACKNOWLEDGE status bit is set: we have noticed the device.

3. The DRIVER status bit is set: we know how to drive the device.

4. Device-specific setup, including reading the device feature
  bits, discovery of virtqueues for the device, optional per-bus
  setup, and reading and possibly writing the device's virtio
  configuration space.

5. The subset of device feature bits understood by the driver is
   written to the device.

6. The DRIVER_OK status bit is set.

7. The device can now be used (ie. buffers added to the

But Linux doesn't do this, and in fact, can't do it easily.  Device initialization includes setting up virtqueues and even (for virtio_blk) scanning the partition table.

Add  a new step, FEATURES_OK, which predates any use and explicitly acks the feature bits.

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]