On Tue, Jun 13, 2023 at 08:30:15PM +0300, Parav Pandit wrote: > --- a/transport-pci.tex > +++ b/transport-pci.tex > @@ -541,6 +541,8 @@ \subsubsection{Notification structure > layout}\label{sec:Virtio Transport Options > struct virtio_pci_notify_cap { > struct virtio_pci_cap cap; > le32 notify_off_multiplier; /* Multiplier for queue_notify_off. */ > + u8 legacy_q_notify_supported; > + u8 reserved[3]; > }; > \end{lstlisting} > > @@ -560,6 +562,14 @@ \subsubsection{Notification structure > layout}\label{sec:Virtio Transport Options > the same Queue Notify address for all queues. > \end{note} > > +\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. -- MST --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org