qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Albert Esteve <aesteve@redhat.com>
Cc: qemu-devel@nongnu.org, slp@redhat.com, hi@alyssa.is,
	mst@redhat.com, Stefano Garzarella <sgarzare@redhat.com>,
	david@redhat.com, stevensd@chromium.org, jasowang@redhat.com
Subject: Re: [PATCH 0/3] Document SHMEM vhost-user requests
Date: Mon, 16 Sep 2024 18:55:54 +0200	[thread overview]
Message-ID: <20240916165554.GD521955@fedora.home> (raw)
In-Reply-To: <20240912144432.126717-1-aesteve@redhat.com>

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

On Thu, Sep 12, 2024 at 04:44:29PM +0200, Albert Esteve wrote:
> As a continuation of the
> "Add SHMEM_MAP/UNMAP requests" patch [1],
> I wanted to split vhost-user spec
> parts into a separate patch, so that
> it could be reviewed and integrated
> separately. Having the specs upstreamed
> would help others to add support for
> these new vhost-user requests on
> their systems.
> 
> This is such documentation-only patch.

The spec changes do not mention that exposing VIRTIO Shared Memory
Regions can lead to problems when other vhost-user devices attempt to
access those memory addresses. Please either introduce MEM_READ/WRITE
and explain its use or document that front-ends must forward mappings to
back-ends so that VIRTIO Shared Memory Regions can be accessed.

> 
> [1] - https://lore.kernel.org/all/20240628145710.1516121-1-aesteve@redhat.com/T/
> 
> Albert Esteve (3):
>   vhost_user.rst: Add SHMEM_MAP/_UNMAP to spec
>   vhost_user.rst: Align VhostUserMsg excerpt members
>   vhost_user.rst: Add GET_SHMEM_CONFIG message
> 
>  docs/interop/vhost-user.rst | 72 +++++++++++++++++++++++++++++++++++++
>  1 file changed, 72 insertions(+)
> 
> -- 
> 2.45.2
> 

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

      parent reply	other threads:[~2024-09-16 16:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 14:44 [PATCH 0/3] Document SHMEM vhost-user requests Albert Esteve
2024-09-12 14:44 ` [PATCH 1/3] vhost_user.rst: Add SHMEM_MAP/_UNMAP to spec Albert Esteve
2024-09-16 16:29   ` Stefan Hajnoczi
2024-09-16 16:35   ` Stefan Hajnoczi
2024-09-12 14:44 ` [PATCH 2/3] vhost_user.rst: Align VhostUserMsg excerpt members Albert Esteve
2024-09-12 14:44 ` [PATCH 3/3] vhost_user.rst: Add GET_SHMEM_CONFIG message Albert Esteve
2024-09-12 16:42   ` Alyssa Ross
2024-09-16 16:34   ` Stefan Hajnoczi
2024-09-12 14:57 ` [PATCH 0/3] Document SHMEM vhost-user requests Albert Esteve
2024-09-16 16:55 ` Stefan Hajnoczi [this message]

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=20240916165554.GD521955@fedora.home \
    --to=stefanha@redhat.com \
    --cc=aesteve@redhat.com \
    --cc=david@redhat.com \
    --cc=hi@alyssa.is \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=slp@redhat.com \
    --cc=stevensd@chromium.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;
as well as URLs for NNTP newsgroup(s).