[virtio-dev] RE: [PATCH v17 03/11] content: Rename confusing queue_notify_data and vqn names

2023-05-15 Thread Parav Pandit
> From: Cornelia Huck > Sent: Monday, May 15, 2023 5:43 AM > > On Fri, May 05 2023, Parav Pandit wrote: > > > diff --git a/content.tex b/content.tex index 9cf938c..327926f 100644 > > --- a/content.tex > > +++ b/content.tex > > @@ -405,8 +405,12 @@ \section{Driver Notifications} \label{sec:Bas

[virtio-dev] Re: [PATCH v17 03/11] content: Rename confusing queue_notify_data and vqn names

2023-05-15 Thread Cornelia Huck
On Fri, May 05 2023, Parav Pandit wrote: > diff --git a/content.tex b/content.tex > index 9cf938c..327926f 100644 > --- a/content.tex > +++ b/content.tex > @@ -405,8 +405,12 @@ \section{Driver Notifications} \label{sec:Basic > Facilities of a Virtio Device / > notification to the device. > >

[virtio-dev] Re: [PATCH v17 03/11] content: Rename confusing queue_notify_data and vqn names

2023-05-05 Thread David Edmondson
Parav Pandit writes: > Currently queue_notify_data register indicates the device > internal queue notification content. This register is > meaningful only when feature bit VIRTIO_F_NOTIF_CONFIG_DATA is > negotiated. > > However, above register name often get confusing association with > very simi