All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: mst@redhat.com, virtio-dev@lists.oasis-open.org,
	cohuck@redhat.com, virtio-comment@lists.oasis-open.org,
	shahafs@nvidia.com
Subject: Re: [virtio-comment] [PATCH] transport-mmio: Replace virtual queue with virtqueue
Date: Wed, 12 Apr 2023 10:51:40 -0400	[thread overview]
Message-ID: <20230412145140.GC2790100@fedora> (raw)
In-Reply-To: <20230411201647.753327-1-parav@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

On Tue, Apr 11, 2023 at 11:16:47PM +0300, Parav Pandit wrote:
> Basic facilities define the virtqueue construct for device <-> driver
> communication.
> 
> PCI transport and individual devices description also refers to it as
> virtqueue.
> 
> MMIO refers to it as 'virtual queue'.
> 
> Align MMIO transport description to call such object a virtqueue.
> 
> This patch is on top of [1].
> 
> [1] https://lists.oasis-open.org/archives/virtio-dev/202304/msg00253.html
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---
>  transport-mmio.tex | 50 +++++++++++++++++++++++-----------------------
>  1 file changed, 25 insertions(+), 25 deletions(-)

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: mst@redhat.com, virtio-dev@lists.oasis-open.org,
	cohuck@redhat.com, virtio-comment@lists.oasis-open.org,
	shahafs@nvidia.com
Subject: [virtio-dev] Re: [virtio-comment] [PATCH] transport-mmio: Replace virtual queue with virtqueue
Date: Wed, 12 Apr 2023 10:51:40 -0400	[thread overview]
Message-ID: <20230412145140.GC2790100@fedora> (raw)
In-Reply-To: <20230411201647.753327-1-parav@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

On Tue, Apr 11, 2023 at 11:16:47PM +0300, Parav Pandit wrote:
> Basic facilities define the virtqueue construct for device <-> driver
> communication.
> 
> PCI transport and individual devices description also refers to it as
> virtqueue.
> 
> MMIO refers to it as 'virtual queue'.
> 
> Align MMIO transport description to call such object a virtqueue.
> 
> This patch is on top of [1].
> 
> [1] https://lists.oasis-open.org/archives/virtio-dev/202304/msg00253.html
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---
>  transport-mmio.tex | 50 +++++++++++++++++++++++-----------------------
>  1 file changed, 25 insertions(+), 25 deletions(-)

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-04-12 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 20:16 [virtio-comment] [PATCH] transport-mmio: Replace virtual queue with virtqueue Parav Pandit
2023-04-11 20:16 ` [virtio-dev] " Parav Pandit
2023-04-12 14:51 ` Stefan Hajnoczi [this message]
2023-04-12 14:51   ` [virtio-dev] Re: [virtio-comment] " Stefan Hajnoczi

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=20230412145140.GC2790100@fedora \
    --to=stefanha@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=parav@nvidia.com \
    --cc=shahafs@nvidia.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.