From: Gerd Hoffmann <kraxel@redhat.com>
To: "Zhang, Tina" <tina.zhang@intel.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Kasireddy, Vivek" <vivek.kasireddy@intel.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Kim, Dongwon" <dongwon.kim@intel.com>
Subject: Re: [RFC 0/1] Use dmabufs for display updates instead of pixman
Date: Fri, 19 Mar 2021 11:45:38 +0100 [thread overview]
Message-ID: <20210319104538.dpoffojh3cu7wax7@sirius.home.kraxel.org> (raw)
In-Reply-To: <BN7PR11MB278631D2E7F4C7F3DCCB0C6D89699@BN7PR11MB2786.namprd11.prod.outlook.com>
> Hi,
> According to
> https://lore.kernel.org/dri-devel/20210212110140.gdpu7kapnr7ovdcn@sirius.home.kraxel.org/
> proposal, we made some progress on making a 'virtio-gpu (display) +
> pass-through GPU' prototype. We leverage the kmsro framework provided
> by mesa to let the virtio-gpu display work with a passed-through GPU
> in headless mode. And the MR is here:
> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9592
Cool.
> Although our work is different from this on-going discussion which is
> about enabling a general way to share buffers between guest and host,
> we'd like to leverage this patch. So, is there any plan to refine this
> patch?
Item (1) on Vivek's new TODO list should provide that. Once we have
shared blob resources we can create udmabufs on the host side, which
in turn allows to drop extra copies in the display path and speed up
this use case as well (both with and without opengl).
take care,
Gerd
prev parent reply other threads:[~2021-03-19 10:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 8:03 [RFC 0/1] Use dmabufs for display updates instead of pixman Vivek Kasireddy
2021-03-02 8:03 ` [RFC 1/1] virtio-gpu: Use dmabuf for display updates if possible " Vivek Kasireddy
2021-03-02 8:29 ` Marc-André Lureau
2021-03-09 8:26 ` Kasireddy, Vivek
2021-03-02 8:21 ` [RFC 0/1] Use dmabufs for display updates " no-reply
2021-03-02 12:03 ` Gerd Hoffmann
2021-03-09 8:18 ` Kasireddy, Vivek
2021-03-09 9:37 ` Gerd Hoffmann
2021-03-17 8:28 ` Kasireddy, Vivek
2021-03-17 14:20 ` Gerd Hoffmann
2021-03-18 23:41 ` Kasireddy, Vivek
2021-03-18 6:24 ` Zhang, Tina
2021-03-19 10:45 ` Gerd Hoffmann [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=20210319104538.dpoffojh3cu7wax7@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dongwon.kim@intel.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tina.zhang@intel.com \
--cc=vivek.kasireddy@intel.com \
/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.