From: Gerd Hoffmann <kraxel@redhat.com>
To: Frank Yang <lfy@google.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Roman Kiryanov <rkir@google.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
virtio-dev@lists.oasis-open.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [virtio-dev] Memory sharing device
Date: Wed, 20 Feb 2019 08:02:13 +0100 [thread overview]
Message-ID: <20190220070213.3uetjgzzlf5qojan@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAEkmjvVA_pxL7FyR4p+u5LH4JfBNOFgAJf-B3573OM58pAD7+A@mail.gmail.com>
> > > In general though, this means that the ideal usage of host pointers would
> > > be to set a few regions up front for certain purposes, then share that
> > out
> > > amongst other device contexts. This also facilitates sharing the memory
> > > between guest processes, which is useful for implementing things like
> > > compositors.
> >
> > Guest processes in the same VM or in different VMs?
> >
>
>
> The guest processes are in the same VM.
> Are you also considering the usage in different VMs?
No, I'm just asking whenever that is important to you.
For communication between guest processes within the same VM I don't
really see a need to involve the hypervisor ...
> > This also features heavily for our "virtio userspace" thing.
> > > Since this is a common pattern, should this sharing concept be
> > standardized
> > > somehow? I.e., should there be a standard way to send Shmid/offset/size
> > to
> > > other devices, or have that be a standard struct in the hypervisor?
> >
> > Same question: other devices of the same VM?
> >
>
> Yes, also, other devices of the same VM.
So why involve the hypervisor here? The guest can handle that on its
own. Passing an image data buffer from the usb webcam to the intel gpu
for display (on bare metal) isn't fundamentally different from passing a
buffer from virtio-camera to virtio-gpu (in a VM). Linux guests will
use dma-bufs for that, other OSes probably something else.
cheers,
Gerd
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2019-02-20 7:02 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 20:34 [virtio-dev] Memory sharing device Roman Kiryanov
2019-02-04 5:40 ` Stefan Hajnoczi
2019-02-04 10:13 ` Gerd Hoffmann
2019-02-04 10:18 ` Roman Kiryanov
2019-02-05 7:42 ` Roman Kiryanov
2019-02-05 10:04 ` Dr. David Alan Gilbert
2019-02-05 15:17 ` Frank Yang
2019-02-05 15:21 ` Frank Yang
2019-02-05 21:06 ` Roman Kiryanov
2019-02-06 7:03 ` Gerd Hoffmann
2019-02-06 15:09 ` Frank Yang
2019-02-06 15:11 ` Frank Yang
2019-02-08 7:57 ` Stefan Hajnoczi
2019-02-08 14:46 ` Frank Yang
2019-02-06 20:14 ` Dr. David Alan Gilbert
2019-02-06 20:27 ` Frank Yang
2019-02-07 12:10 ` Cornelia Huck
2019-02-11 14:49 ` Michael S. Tsirkin
2019-02-11 15:14 ` Frank Yang
2019-02-11 15:25 ` Frank Yang
2019-02-12 13:01 ` Michael S. Tsirkin
2019-02-12 13:16 ` Dr. David Alan Gilbert
2019-02-12 13:27 ` Michael S. Tsirkin
2019-02-12 16:17 ` Frank Yang
2019-02-19 7:17 ` Gerd Hoffmann
2019-02-19 15:59 ` Frank Yang
2019-02-20 6:51 ` Gerd Hoffmann
2019-02-20 15:31 ` Frank Yang
2019-02-21 6:55 ` Gerd Hoffmann
2019-02-19 7:12 ` Gerd Hoffmann
2019-02-19 16:02 ` Frank Yang
2019-02-20 7:02 ` Gerd Hoffmann [this message]
2019-02-20 15:32 ` Frank Yang
2019-02-21 7:29 ` Gerd Hoffmann
2019-02-21 9:24 ` Dr. David Alan Gilbert
2019-02-21 9:59 ` Gerd Hoffmann
2019-02-21 10:03 ` Dr. David Alan Gilbert
2019-02-22 6:15 ` Michael S. Tsirkin
2019-02-22 6:42 ` Gerd Hoffmann
2019-02-11 16:57 ` Michael S. Tsirkin
2019-02-12 8:27 ` Roman Kiryanov
2019-02-12 11:25 ` Dr. David Alan Gilbert
2019-02-12 13:47 ` Cornelia Huck
2019-02-12 14:03 ` Michael S. Tsirkin
2019-02-12 15:56 ` Frank Yang
2019-02-12 16:46 ` Dr. David Alan Gilbert
2019-02-12 17:20 ` Frank Yang
2019-02-12 17:26 ` Frank Yang
2019-02-12 19:06 ` Michael S. Tsirkin
2019-02-13 2:50 ` Frank Yang
2019-02-13 4:02 ` Michael S. Tsirkin
2019-02-13 4:19 ` Michael S. Tsirkin
2019-02-13 4:59 ` Frank Yang
2019-02-13 18:18 ` Frank Yang
2019-02-14 7:15 ` Frank Yang
2019-02-22 22:05 ` Michael S. Tsirkin
2019-02-24 21:19 ` Frank Yang
2019-02-13 4:59 ` Frank Yang
2019-02-19 7:54 ` Gerd Hoffmann
2019-02-19 15:54 ` Frank Yang
2019-02-20 3:46 ` Michael S. Tsirkin
2019-02-20 15:24 ` Frank Yang
2019-02-20 19:29 ` Michael S. Tsirkin
2019-02-20 6:25 ` Gerd Hoffmann
2019-02-20 15:30 ` Frank Yang
2019-02-20 15:35 ` Frank Yang
2019-02-21 6:44 ` Gerd Hoffmann
2019-02-12 18:22 ` Michael S. Tsirkin
2019-02-12 19:01 ` Frank Yang
2019-02-12 19:15 ` Michael S. Tsirkin
2019-02-12 20:15 ` Frank Yang
2019-02-12 13:00 ` Michael S. Tsirkin
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=20190220070213.3uetjgzzlf5qojan@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lfy@google.com \
--cc=mst@redhat.com \
--cc=rkir@google.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 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.