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

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-dev message

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


Subject: Re: [PATCH] virtio-pci: implement VIRTIO_F_RING_STATE



在 2021/7/9 下午7:06, Cornelia Huck 写道:
On Wed, Jul 07 2021, Jason Wang <jasowang@redhat.com> wrote:

This patch is a follow up for the virtqueue state synchronization
series to implement VIRTIO_F_RING_STATE via a dedicated capability for
PCI transport.

With the help of the STOP status bit, the virtqueue state
synchronization for PCI should be self contained.

Signed-off-by: Jason Wang <jasowang@redhat.com>
---
  content.tex | 32 ++++++++++++++++++++++++++++++++
  1 file changed, 32 insertions(+)
(...)

+\devicenormative{\paragraph}{General Virtqueue State}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / General Virtqueue State}
+
+The device MUST present at least one VIRTIO_PCI_CAP_RING_STATE
capability if VITIO_F_RING_STATE is negotiated.
s/VITIO/VIRTIO/


Will fix.



Are multiple capabilities inteded to enable parallel access to multiple
virtqueues?


I'm not sure, it just not forbid the device to have multiple of such capabilies. We've already had normative like this for common configuration structure:

"The device MUST present at least one common configuration capability."

Thanks



+
  \subsubsection{Legacy Interfaces: A Note on PCI Device Layout}\label{sec:Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Legacy Interfaces: A Note on PCI Device Layout}
Transitional devices MUST present part of configuration



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