From: Gerd Hoffmann <kraxel@redhat.com>
To: Antonio Caggiano <antonio.caggiano@collabora.com>
Cc: qemu-devel@nongnu.org, gert.wollny@collabora.com,
dmitry.osipenko@collabora.com,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v2 4/4] virtio-gpu: Don't require udmabuf when blob support is enabled
Date: Fri, 23 Sep 2022 14:32:19 +0200 [thread overview]
Message-ID: <20220923123219.ofn2ygm4knljo6w2@sirius.home.kraxel.org> (raw)
In-Reply-To: <20220913105022.81953-5-antonio.caggiano@collabora.com>
On Tue, Sep 13, 2022 at 12:50:22PM +0200, Antonio Caggiano wrote:
> From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
>
> Host blobs don't need udmabuf, it's only needed by guest blobs. The host
> blobs are utilized by the Mesa virgl driver when persistent memory mapping
> is needed by a GL buffer, otherwise virgl driver doesn't use blobs.
> Persistent mapping support bumps GL version from 4.3 to 4.5 in guest.
> Relax the udmabuf requirement.
What about blob=on,virgl=off?
In that case qemu manages the resources and continued to require
udmabuf.
Patches 1-3 look good, queued them up.
thanks,
Gerd
next prev parent reply other threads:[~2022-09-23 12:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 10:50 [PATCH v2 0/4] virtio-gpu: Blob resources Antonio Caggiano
2022-09-13 10:50 ` [PATCH v2 1/4] virtio: Add shared memory capability Antonio Caggiano
2022-09-13 13:48 ` Bin Meng
2022-09-13 10:50 ` [PATCH v2 2/4] virtio-gpu: hostmem Antonio Caggiano
2022-09-13 10:50 ` [PATCH v2 3/4] virtio-gpu: Handle resource blob commands Antonio Caggiano
2022-09-13 10:50 ` [PATCH v2 4/4] virtio-gpu: Don't require udmabuf when blob support is enabled Antonio Caggiano
2022-09-23 12:32 ` Gerd Hoffmann [this message]
2022-09-26 18:32 ` Dmitry Osipenko
2022-09-27 8:32 ` Gerd Hoffmann
2022-09-27 10:44 ` Dmitry Osipenko
2022-09-27 21:57 ` Kasireddy, Vivek
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=20220923123219.ofn2ygm4knljo6w2@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=antonio.caggiano@collabora.com \
--cc=dmitry.osipenko@collabora.com \
--cc=gert.wollny@collabora.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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).