All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhu, Lingshan" <lingshan.zhu@intel.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: jasowang@redhat.com, mst@redhat.com, eperezma@redhat.com,
	cohuck@redhat.com, virtio-comment@lists.oasis-open.org,
	virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-comment] Re: [virtio-dev] [RFC PATCH 5/5] virtio-pci: implement VIRTIO_F_QUEUE_STATE
Date: Tue, 15 Aug 2023 19:31:14 +0800	[thread overview]
Message-ID: <3f5e34be-9c6d-cf83-96b8-ef8660962727@intel.com> (raw)
In-Reply-To: <20230814151820.GH3146793@fedora>



On 8/14/2023 11:18 PM, Stefan Hajnoczi wrote:
> On Tue, Aug 15, 2023 at 03:29:04AM +0800, Zhu Lingshan wrote:
>> This patch adds two new le16 fields to common configruation structure
>> to support VIRTIO_F_QUEUE_STATE in PCI tranport layer.
>>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
>> ---
>>   transport-pci.tex | 15 +++++++++++++++
>>   1 file changed, 15 insertions(+)
>>
>> diff --git a/transport-pci.tex b/transport-pci.tex
>> index a5c6719..d9bccb0 100644
>> --- a/transport-pci.tex
>> +++ b/transport-pci.tex
>> @@ -321,6 +321,8 @@ \subsubsection{Common configuration structure layout}\label{sec:Virtio Transport
>>           le64 queue_device;              /* read-write */
>>           le16 queue_notif_config_data;   /* read-only for driver */
>>           le16 queue_reset;               /* read-write */
>> +        le16 queue_avail_state;         /* read-write */
>> +        le16 queue_used_state;          /* read-write */
>>   
>>           /* About the administration virtqueue. */
>>           le16 admin_queue_index;         /* read-only for driver */
> This is an incompatible change to the register layout. Please add new
> registers at the end of struct virtio_pci_common_cfg so field offsets
> don't change for existing drivers and devices.
Oh yes, I missed that, thanks
>> @@ -415,6 +417,16 @@ \subsubsection{Common configuration structure layout}\label{sec:Virtio Transport
>>           This field exists only if VIRTIO_F_RING_RESET has been
>>           negotiated. (see \ref{sec:Basic Facilities of a Virtio Device / Virtqueues / Virtqueue Reset}).
>>   
>> +\item[\field{queue_avail_state}]
>> +        This field is vaild only if VIRTIO_F_QUEUE_STATE has been
> "valid"
yes
>
>> +        negotiated. The driver sets and gets the available state of
>> +        the virtqueue here (see \ref{sec:Virtqueues / Virtqueue State}).
>> +
>> +\item[\field{queue_used_state}]
>> +        This field is vaild only if VIRTIO_F_QUEUE_STATE has been
> "valid"
yes
>
>> +        negotiated. The driver sets and gets the used state of the
>> +        virtqueue here (see \ref{sec:Virtqueues / Virtqueue State}).
>> +
>>   \item[\field{admin_queue_index}]
>>           The device uses this to report the index of the first administration virtqueue.
>>           This field is valid only if VIRTIO_F_ADMIN_VQ has been negotiated.
>> @@ -488,6 +500,9 @@ \subsubsection{Common configuration structure layout}\label{sec:Virtio Transport
>>   present either a value of 0 or a power of 2 in
>>   \field{queue_size}.
>>   
>> +If VIRTIO_F_QUEUE_STATE has not been negotiated, the device MUST ignore
>> +any accesses against \field{queue_avail_state} and \field{queue_used_state}.
> "accesses to"
Yes, thanks for your review
>
>> +
>>   If VIRTIO_F_ADMIN_VQ has been negotiated, the value
>>   \field{admin_queue_index} MUST be equal to, or bigger than
>>   \field{num_queues}; also, \field{admin_queue_num} MUST be
>> -- 
>> 2.35.3
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
>>


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


WARNING: multiple messages have this Message-ID (diff)
From: "Zhu, Lingshan" <lingshan.zhu@intel.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: jasowang@redhat.com, mst@redhat.com, eperezma@redhat.com,
	cohuck@redhat.com, virtio-comment@lists.oasis-open.org,
	virtio-dev@lists.oasis-open.org
Subject: [virtio-dev] Re: [virtio-comment] Re: [virtio-dev] [RFC PATCH 5/5] virtio-pci: implement VIRTIO_F_QUEUE_STATE
Date: Tue, 15 Aug 2023 19:31:14 +0800	[thread overview]
Message-ID: <3f5e34be-9c6d-cf83-96b8-ef8660962727@intel.com> (raw)
In-Reply-To: <20230814151820.GH3146793@fedora>



On 8/14/2023 11:18 PM, Stefan Hajnoczi wrote:
> On Tue, Aug 15, 2023 at 03:29:04AM +0800, Zhu Lingshan wrote:
>> This patch adds two new le16 fields to common configruation structure
>> to support VIRTIO_F_QUEUE_STATE in PCI tranport layer.
>>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
>> ---
>>   transport-pci.tex | 15 +++++++++++++++
>>   1 file changed, 15 insertions(+)
>>
>> diff --git a/transport-pci.tex b/transport-pci.tex
>> index a5c6719..d9bccb0 100644
>> --- a/transport-pci.tex
>> +++ b/transport-pci.tex
>> @@ -321,6 +321,8 @@ \subsubsection{Common configuration structure layout}\label{sec:Virtio Transport
>>           le64 queue_device;              /* read-write */
>>           le16 queue_notif_config_data;   /* read-only for driver */
>>           le16 queue_reset;               /* read-write */
>> +        le16 queue_avail_state;         /* read-write */
>> +        le16 queue_used_state;          /* read-write */
>>   
>>           /* About the administration virtqueue. */
>>           le16 admin_queue_index;         /* read-only for driver */
> This is an incompatible change to the register layout. Please add new
> registers at the end of struct virtio_pci_common_cfg so field offsets
> don't change for existing drivers and devices.
Oh yes, I missed that, thanks
>> @@ -415,6 +417,16 @@ \subsubsection{Common configuration structure layout}\label{sec:Virtio Transport
>>           This field exists only if VIRTIO_F_RING_RESET has been
>>           negotiated. (see \ref{sec:Basic Facilities of a Virtio Device / Virtqueues / Virtqueue Reset}).
>>   
>> +\item[\field{queue_avail_state}]
>> +        This field is vaild only if VIRTIO_F_QUEUE_STATE has been
> "valid"
yes
>
>> +        negotiated. The driver sets and gets the available state of
>> +        the virtqueue here (see \ref{sec:Virtqueues / Virtqueue State}).
>> +
>> +\item[\field{queue_used_state}]
>> +        This field is vaild only if VIRTIO_F_QUEUE_STATE has been
> "valid"
yes
>
>> +        negotiated. The driver sets and gets the used state of the
>> +        virtqueue here (see \ref{sec:Virtqueues / Virtqueue State}).
>> +
>>   \item[\field{admin_queue_index}]
>>           The device uses this to report the index of the first administration virtqueue.
>>           This field is valid only if VIRTIO_F_ADMIN_VQ has been negotiated.
>> @@ -488,6 +500,9 @@ \subsubsection{Common configuration structure layout}\label{sec:Virtio Transport
>>   present either a value of 0 or a power of 2 in
>>   \field{queue_size}.
>>   
>> +If VIRTIO_F_QUEUE_STATE has not been negotiated, the device MUST ignore
>> +any accesses against \field{queue_avail_state} and \field{queue_used_state}.
> "accesses to"
Yes, thanks for your review
>
>> +
>>   If VIRTIO_F_ADMIN_VQ has been negotiated, the value
>>   \field{admin_queue_index} MUST be equal to, or bigger than
>>   \field{num_queues}; also, \field{admin_queue_num} MUST be
>> -- 
>> 2.35.3
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2023-08-15 11:31 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 19:28 [virtio-comment] [RFC PATCH 0/5] virtio: introduce SUSPEND bit and vq state Zhu Lingshan
2023-08-14 19:28 ` [virtio-dev] " Zhu Lingshan
2023-08-14 14:20 ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 14:20   ` [virtio-dev] " Stefan Hajnoczi
2023-08-14 15:47 ` Stefan Hajnoczi
2023-08-14 15:47   ` [virtio-dev] " Stefan Hajnoczi
2023-08-15  1:38   ` Jason Wang
2023-08-15  1:38     ` [virtio-dev] " Jason Wang
2023-08-15 10:14     ` Zhu, Lingshan
2023-08-15 10:14       ` [virtio-dev] " Zhu, Lingshan
2023-08-14 19:29 ` [virtio-comment] [RFC PATCH 1/5] virtio: introduce SUSPEND bit in device status Zhu Lingshan
2023-08-14 19:29   ` [virtio-dev] " Zhu Lingshan
2023-08-14 14:30   ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 14:30     ` [virtio-dev] " Stefan Hajnoczi
2023-08-15 10:31     ` Zhu, Lingshan
2023-08-15 10:31       ` [virtio-dev] " Zhu, Lingshan
2023-08-15 12:29       ` Stefan Hajnoczi
2023-08-15 12:29         ` [virtio-dev] " Stefan Hajnoczi
2023-08-17 15:15         ` Eugenio Perez Martin
2023-08-17 15:15           ` [virtio-dev] " Eugenio Perez Martin
2023-08-17 16:04           ` Stefan Hajnoczi
2023-08-17 16:04             ` [virtio-dev] " Stefan Hajnoczi
2023-08-18  9:55             ` Zhu, Lingshan
2023-08-18  9:55               ` [virtio-dev] " Zhu, Lingshan
2023-08-21 13:45               ` Stefan Hajnoczi
2023-08-21 13:45                 ` [virtio-dev] " Stefan Hajnoczi
2023-08-15  0:26   ` [virtio-comment] " Jason Wang
2023-08-15  0:26     ` [virtio-dev] " Jason Wang
2023-08-15  0:37     ` [virtio-comment] " Jason Wang
2023-08-15  0:37       ` [virtio-dev] " Jason Wang
2023-08-15 10:48       ` [virtio-comment] " Zhu, Lingshan
2023-08-15 10:48         ` [virtio-dev] " Zhu, Lingshan
2023-08-16  1:58         ` [virtio-comment] " Jason Wang
2023-08-16  1:58           ` [virtio-dev] " Jason Wang
2023-08-16  2:17           ` [virtio-comment] " Zhu, Lingshan
2023-08-16  2:17             ` [virtio-dev] " Zhu, Lingshan
2023-08-15 10:50       ` [virtio-comment] " Zhu, Lingshan
2023-08-15 10:50         ` [virtio-dev] " Zhu, Lingshan
2023-08-16  2:05         ` [virtio-comment] " Jason Wang
2023-08-16  2:05           ` [virtio-dev] " Jason Wang
2023-08-16  2:20           ` Zhu, Lingshan
2023-08-16  2:20             ` [virtio-dev] " Zhu, Lingshan
2023-08-14 19:29 ` [virtio-comment] [RFC PATCH 2/5] virtio: introduce vq state as basic facility Zhu Lingshan
2023-08-14 19:29   ` [virtio-dev] " Zhu Lingshan
2023-08-14 14:49   ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 14:49     ` Stefan Hajnoczi
2023-08-15 10:53     ` [virtio-comment] " Zhu, Lingshan
2023-08-15 10:53       ` Zhu, Lingshan
2023-08-14 19:29 ` [virtio-comment] [RFC PATCH 3/5] virtio: The actions by the device upon SUSPEND Zhu Lingshan
2023-08-14 19:29   ` [virtio-dev] " Zhu Lingshan
2023-08-14 15:00   ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 15:00     ` [virtio-dev] " Stefan Hajnoczi
2023-08-15 11:07     ` Zhu, Lingshan
2023-08-15 11:07       ` [virtio-dev] " Zhu, Lingshan
2023-08-15 12:33       ` Stefan Hajnoczi
2023-08-15 12:33         ` [virtio-dev] " Stefan Hajnoczi
2023-08-16  4:25         ` Zhu, Lingshan
2023-08-16  4:25           ` [virtio-dev] " Zhu, Lingshan
2023-08-16 12:33           ` Stefan Hajnoczi
2023-08-16 12:33             ` [virtio-dev] " Stefan Hajnoczi
2023-08-15  0:29   ` [virtio-comment] " Jason Wang
2023-08-15  0:29     ` [virtio-dev] " Jason Wang
2023-08-15 11:16     ` [virtio-comment] " Zhu, Lingshan
2023-08-15 11:16       ` Zhu, Lingshan
2023-08-16  2:10       ` [virtio-comment] " Jason Wang
2023-08-16  2:10         ` Jason Wang
2023-08-16  4:53         ` [virtio-comment] " Zhu, Lingshan
2023-08-16  4:53           ` Zhu, Lingshan
2023-08-14 19:29 ` [virtio-comment] [RFC PATCH 4/5] virtqueue: constraints for virtqueue state Zhu Lingshan
2023-08-14 19:29   ` [virtio-dev] " Zhu Lingshan
2023-08-14 15:15   ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 15:15     ` Stefan Hajnoczi
2023-08-15 11:18     ` [virtio-comment] " Zhu, Lingshan
2023-08-15 11:18       ` Zhu, Lingshan
2023-08-15  0:34   ` [virtio-comment] " Jason Wang
2023-08-15  0:34     ` [virtio-dev] " Jason Wang
2023-08-15 11:30     ` [virtio-comment] " Zhu, Lingshan
2023-08-15 11:30       ` [virtio-dev] " Zhu, Lingshan
2023-08-16  2:11       ` [virtio-comment] " Jason Wang
2023-08-16  2:11         ` [virtio-dev] " Jason Wang
2023-08-16  5:07         ` [virtio-comment] " Zhu, Lingshan
2023-08-16  5:07           ` Zhu, Lingshan
2023-08-17  8:31       ` [virtio-comment] " Uminski, Piotr
2023-08-17  8:42         ` Zhu, Lingshan
2023-08-17  8:42           ` [virtio-dev] " Zhu, Lingshan
2023-08-21  4:03           ` Jason Wang
2023-08-21  4:03             ` [virtio-dev] " Jason Wang
2023-08-17 15:19       ` Eugenio Perez Martin
2023-08-17 15:19         ` [virtio-dev] " Eugenio Perez Martin
2023-08-18  9:44         ` [virtio-comment] " Zhu, Lingshan
2023-08-18  9:44           ` [virtio-dev] " Zhu, Lingshan
2023-08-21  9:26           ` [virtio-comment] " Eugenio Perez Martin
2023-08-21  9:26             ` [virtio-dev] " Eugenio Perez Martin
2023-08-21 10:32             ` [virtio-comment] " Zhu, Lingshan
2023-08-21 10:32               ` [virtio-dev] " Zhu, Lingshan
2023-09-05  9:08             ` Zhu, Lingshan
2023-09-05  9:08               ` [virtio-dev] " Zhu, Lingshan
2023-09-07  8:09               ` Eugenio Perez Martin
2023-09-07  8:09                 ` [virtio-dev] " Eugenio Perez Martin
2023-09-07  9:34                 ` Zhu, Lingshan
2023-09-07  9:34                   ` [virtio-dev] " Zhu, Lingshan
2023-09-08  6:23                   ` Si-Wei Liu
2023-09-08  6:23                     ` [virtio-dev] " Si-Wei Liu
2023-09-08  8:41                     ` Zhu, Lingshan
2023-09-08  8:41                       ` [virtio-dev] " Zhu, Lingshan
2023-08-14 19:29 ` [virtio-comment] [RFC PATCH 5/5] virtio-pci: implement VIRTIO_F_QUEUE_STATE Zhu Lingshan
2023-08-14 19:29   ` [virtio-dev] " Zhu Lingshan
2023-08-14 15:18   ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 15:18     ` Stefan Hajnoczi
2023-08-15 11:31     ` Zhu, Lingshan [this message]
2023-08-15 11:31       ` [virtio-dev] Re: [virtio-comment] " Zhu, Lingshan
2023-08-15  0:35   ` [virtio-comment] " Jason Wang
2023-08-15  0:35     ` [virtio-dev] " Jason Wang
2023-08-15 11:31     ` [virtio-comment] " Zhu, Lingshan
2023-08-15 11:31       ` [virtio-dev] " Zhu, Lingshan
2023-08-17  3:04 ` [virtio-comment] Re: [RFC PATCH 0/5] virtio: introduce SUSPEND bit and vq state Zhu, Lingshan
2023-08-17  3:04   ` [virtio-dev] " Zhu, Lingshan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3f5e34be-9c6d-cf83-96b8-ef8660962727@intel.com \
    --to=lingshan.zhu@intel.com \
    --cc=cohuck@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.