Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Nikos Dragazis <ndragazis@arrikto.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] [PATCH v5 02/10] vhost-user: minor fixes
Date: Thu, 16 Jul 2020 17:48:24 +0100	[thread overview]
Message-ID: <87sgdrv21z.fsf@linaro.org> (raw)
In-Reply-To: <20200518203721.7625-3-ndragazis@arrikto.com>


Nikos Dragazis <ndragazis@arrikto.com> writes:

> Signed-off-by: Nikos Dragazis <ndragazis@arrikto.com>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
>  virtio-vhost-user.tex | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/virtio-vhost-user.tex b/virtio-vhost-user.tex
> index ac96dc2..13ecd41 100644
> --- a/virtio-vhost-user.tex
> +++ b/virtio-vhost-user.tex
> @@ -231,7 +231,7 @@ \subsubsection{Doorbell structure layout}\label{sec:Device Types / Vhost-user De
>  \end{lstlisting}
>  
>  The \field{cap.offset} and \field{doorbell_off_multiplier} are taken from the
> -notification capability structure above, and the \field{doorbell_idx} is the
> +doorbell capability structure above, and the \field{doorbell_idx} is the
>  doorbell number.

I think it would be helpful to add what we mean by doorbell and
notification into the terminology section at the front of the document?

>  
>  \devicenormative{\paragraph}{Doorbell capability}{Device Types / Vhost-user Device Backend / Additional Device Resources over PCI / Doorbell capability}
> @@ -260,7 +260,7 @@ \subsubsection{Notification structure layout}\label{sec:Device Types / Vhost-use
>  notification interrupts.  If MSI-X is not available, bit 2 of the ISR status
>  indicates that a notification occurred.
>  
> -The notification structure is found using the VIRTIO_PCI_CAP_DOORBELL_CFG
> +The notification structure is found using the VIRTIO_PCI_CAP_NOTIFICATION_CFG
>  capability.
>  
>  \begin{lstlisting}


-- 
Alex Bennée

---------------------------------------------------------------------
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:[~2020-07-16 16:48 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 20:37 [virtio-dev] [PATCH v5 00/10] introduce virtio vhost-user backend device type Nikos Dragazis
2020-05-18 20:37 ` [virtio-dev] [PATCH v5 01/10] vhost-user: add vhost-user " Nikos Dragazis
2020-07-16 16:45   ` Alex Bennée
2020-07-17  9:26     ` Stefan Hajnoczi
2020-07-17 10:28       ` Alex Bennée
2020-07-17 11:17       ` Nikos Dragazis
2020-07-20  9:37         ` Alex Bennée
2020-07-21 11:42           ` Nikos Dragazis
2020-07-23  6:15         ` Stefan Hajnoczi
2020-07-24 13:14           ` Nikos Dragazis
2020-07-24 14:41       ` Michael S. Tsirkin
2020-07-24 17:31         ` Nikos Dragazis
2020-07-27 12:25           ` Stefan Hajnoczi
2020-07-27 18:59             ` Nikos Dragazis
2020-07-29 13:52               ` Michael S. Tsirkin
2020-07-29 21:05                 ` Nikos Dragazis
2020-08-24 14:43                   ` Nikos Dragazis
2020-07-17 16:52     ` Nikos Dragazis
2020-05-18 20:37 ` [virtio-dev] [PATCH v5 02/10] vhost-user: minor fixes Nikos Dragazis
2020-07-16 16:48   ` Alex Bennée [this message]
2020-07-17  9:27   ` Stefan Hajnoczi
2020-05-18 20:37 ` [virtio-dev] [PATCH v5 03/10] vhost-user: add requirements for the notification capability Nikos Dragazis
2020-07-17  9:34   ` Stefan Hajnoczi
2020-07-17 16:02     ` Nikos Dragazis
2020-07-23  6:16       ` Stefan Hajnoczi
2020-05-18 20:37 ` [virtio-dev] [PATCH v5 04/10] vhost-user: update shared memory capability Nikos Dragazis
2020-07-17  9:36   ` Stefan Hajnoczi
2020-07-17 15:00     ` Nikos Dragazis
2020-05-18 20:37 ` [virtio-dev] [PATCH v5 05/10] vhost-user: add conformance targets and clauses Nikos Dragazis
2020-07-17  9:37   ` Stefan Hajnoczi
2020-07-20 15:01   ` Alex Bennée
2020-05-18 20:37 ` [virtio-dev] [PATCH v5 06/10] vhost-user: change the device id Nikos Dragazis
2020-07-20 15:03   ` Alex Bennée
2020-05-18 20:37 ` [virtio-dev] [PATCH v5 07/10] vhost-user: minor fix on status register Nikos Dragazis
2020-07-17  9:39   ` Stefan Hajnoczi
2020-05-18 20:37 ` [virtio-dev] [PATCH v5 08/10] vhost-user: remove the extra PCI capabilities Nikos Dragazis
2020-07-17  9:48   ` Stefan Hajnoczi
2020-07-17 15:03     ` Nikos Dragazis
2020-07-23  6:29       ` Stefan Hajnoczi
2020-07-24 13:41         ` Nikos Dragazis
2020-05-18 20:37 ` [virtio-dev] [PATCH v5 09/10] vhost-user: intercept slave's reply to VHOST_USER_GET_PROTOCOL_FEATURES Nikos Dragazis
2020-07-17  9:57   ` Stefan Hajnoczi
2020-07-17 15:37     ` Nikos Dragazis
2020-07-23  6:32       ` Stefan Hajnoczi
2020-05-18 20:37 ` [virtio-dev] [PATCH v5 10/10] vhost-user: clarify that we are talking about slave-initiated messages Nikos Dragazis
2020-07-17  9:59   ` Stefan Hajnoczi
2020-06-24 18:01 ` [virtio-dev] [PATCH v5 00/10] introduce virtio vhost-user backend device type Nikos Dragazis

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=87sgdrv21z.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=mst@redhat.com \
    --cc=ndragazis@arrikto.com \
    --cc=stefanha@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox