From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Roman Kiryanov <rkir@google.com>,
virtio-dev@lists.oasis-open.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [virtio-dev] Memory sharing device
Date: Mon, 4 Feb 2019 11:13:16 +0100 [thread overview]
Message-ID: <20190204101316.4e3e6rj32suwdmur@sirius.home.kraxel.org> (raw)
In-Reply-To: <20190204054053.GE29758@stefanha-x1.localdomain>
On Mon, Feb 04, 2019 at 01:40:53PM +0800, Stefan Hajnoczi wrote:
> On Fri, Feb 01, 2019 at 12:34:07PM -0800, Roman Kiryanov wrote:
> > for our purposes we need to access host's memory (e.g. Vulkan buffers,
> > but we also considering other things, like running all drivers in
> > userspace) directly from a linux guest (Android). I implemented a
> > device in QEMU and a linux driver for it:
> >
> > https://android.googlesource.com/kernel/goldfish/+/android-goldfish-4.14-dev/drivers/misc/goldfish_address_space.c
> >
> > https://android.googlesource.com/platform/external/qemu/+/emu-master-dev/hw/pci/goldfish_address_space.c
> >
> > during upstreaming the driver it was suggested that developing a
> > virtio spec could be a better approach than inventing our specific
> > driver and device.
> >
> > Could you please advise how to start?
>
> Hi Roman,
> David Gilbert, Gerd Hoffmann, and I have discussed adding shared memory
> resources to VIRTIO. That means memory made available by the device to
> the driver instead of the usual other way around.
>
> virtio-gpu needs this and perhaps that use case overlaps with yours too.
virtio-gpu specifically needs that to support vulkan and opengl
extensions for coherent buffers, which must be allocated by the host gpu
driver. It's WIP still.
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-04 10:13 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 [this message]
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
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=20190204101316.4e3e6rj32suwdmur@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=dgilbert@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.