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

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

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


Subject: RE: [PATCH v6 4/4] transport-pci: Introduce group legacy group member config region access



> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Monday, June 19, 2023 12:38 PM

> >
> > +\field{legacy_q_notify_supported} when set to 1, indicates that the
> > +device supports legacy queue notifications at this notification
> > +location. Legacy Queue Notification address is derived within a BAR for a
> virtqueue:
> > +
> > +\begin{lstlisting}
> > +        cap.offset
> > +\end{lstlisting}
> > +
> >  \devicenormative{\paragraph}{Notification capability}{Virtio
> > Transport Options / Virtio Over PCI Bus / PCI Device Layout / Notification
> capability}  The device MUST present at least one notification capability.
> >
> 
> I was hoping that we can avoid touching transport-pci.tex completely, this is
> why I wanted to reuse VIRTIO_PCI_CAP_NOTIFY_CFG.

It is reused, but it doesnt come for free.
Do you want to re-consider AQ notify query command?
Or continue as proposed in v6?


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