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] (VIRTIO-134) Make it clear how chained indirect descriptors must work.


     [ https://issues.oasis-open.org/browse/VIRTIO-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Tsirkin updated VIRTIO-134:
-----------------------------------

    Fix Version/s: virtio 1.0 cs03

> Make it clear how chained indirect descriptors must work.
> ---------------------------------------------------------
>
>                 Key: VIRTIO-134
>                 URL: https://issues.oasis-open.org/browse/VIRTIO-134
>             Project: OASIS Virtual I/O Device (VIRTIO) TC
>          Issue Type: Bug
>    Affects Versions: virtio 1.0 csprd03, virtio 1.0 cs01, virtio 1.0 cs02
>            Reporter: Rusty Russell
>             Fix For: virtio 1.0 cs03
>
>
> Chained indirect descriptors were partially banned by virtio-15, which said how devices would handle them (by terminating the descriptor when it hits the end of the indirect descriptors).  It didn't spell out that (obviously) they shouldn't be generated by drivers!
> It also leaves open the possibility of one or more direct descriptors followed by a trailing indirect descriptor.  All implementations I know of handle this, though none I know of generate such things.  My test lguest implementation didn't (now fixed); we should spell out explicitly that it's possible.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


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