From: "Michael S. Tsirkin" <mst@redhat.com>
To: Frank Yang <lfy@google.com>
Cc: Roman Kiryanov <rkir@google.com>,
Gerd Hoffmann <kraxel@redhat.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: Mon, 11 Feb 2019 11:57:50 -0500 [thread overview]
Message-ID: <20190211103652-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAEkmjvVzmfUmu3DDXSSPqTBqXNMyp65sy28xhSiigRGftGiyXw@mail.gmail.com>
On Mon, Feb 11, 2019 at 07:14:53AM -0800, Frank Yang wrote:
>
>
> On Mon, Feb 11, 2019 at 6:49 AM Michael S. Tsirkin <mst@redhat.com> wrote:
>
> On Mon, Feb 04, 2019 at 11:42:25PM -0800, Roman Kiryanov wrote:
> > Hi Gerd,
> >
> > > 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.
> >
> > the proposed spec says:
> >
> > +Shared memory regions MUST NOT be used to control the operation
> > +of the device, nor to stream data; those should still be performed
> > +using virtqueues.
> >
> > Is there a strong reason to prohibit using memory regions for control
> purposes?
>
> That's in order to make virtio have portability implications, such that if
> people see a virtio device in lspci they know there's
> no lock-in, their guest can be moved between hypervisors
> and will still work.
>
> > Our long term goal is to have as few kernel drivers as possible and to
> move
> > "drivers" into userspace. If we go with the virtqueues, is there
> > general a purpose
> > device/driver to talk between our host and guest to support custom
> hardware
> > (with own blobs)?
>
> The challenge is to answer the following question:
> how to do this without losing the benefits of standartization?
>
>
> Draft spec is incoming, but the basic idea is to standardize how to enumerate,
> discover, and operate (with high performance) such userspace drivers/devices;
> the basic operations would be standardized, and userspace drivers would be
> constructed out of the resulting primitives.
As long standartization facilitates functionality, e.g.
if we can support moving between hypervisors, this seems
in-scope for virtio.
> > Could you please advise if we can use something else to
> > achieve this goal?
>
> I am not sure what the goal is though. Blobs is a means I guess
> or it should be :) E.g. is it about being able to iterate quickly?
>
> Maybe you should look at vhost-user-gpu patches on qemu?
> Would this address your need?
> Acks for these patches would be a good thing.
>
>
>
> Is this it:
>
> https://patchwork.kernel.org/patch/10444089/ ?
>
> I'll check it out and try to discuss. Is there a draft spec for it as well?
virtio gpu is part of the csprd01 draft.
>
>
> --
> MST
>
---------------------------------------------------------------------
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-11 16:58 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
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 [this message]
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=20190211103652-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=lfy@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox