dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Huang, Honglei" <honghuan@amd.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Akihiko Odaki" <odaki@rsg.ci.i.u-tokyo.ac.jp>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Stefano Garzarella" <sgarzare@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"David Airlie" <airlied@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, virtio-comment@lists.oasis-open.org,
	dri-devel@lists.freedesktop.org, virtualization@lists.linux.dev,
	Honglei Huang <honglei1.huang@amd.com>,
	Huang Rui <Ray.Huang@amd.com>
Subject: Re: About new backend for GPU compute ROCm in qemu
Date: Mon, 7 Sep 2026 16:05:50 +0300	[thread overview]
Message-ID: <fc5c5bc5-d3a5-47f4-8a86-bcd531f0803c@collabora.com> (raw)
In-Reply-To: <ba0b1bbf-5ebf-4ac3-9f7b-8740e3bc283b@amd.com>

On 8/17/26 06:19, Huang, Honglei wrote:
> Hi Michael, Alex, Dmitry, Akihiko,
> 
> I'm bringing AMD GPU compute ROCm based on virtio. I posted a ROCm over
> virtio
> implementation to virglrenderer nine months ago (MR !1568 [1]). The ROCm
> side has
> been supportted by ROCm offical.
> 
> Current implementation is a virtio gpu context type capset handled inside
> virglrenderer, sharing the display path. That's an awkward fit, many
> compute GPUs have no display engine at all.

The headless context type is totally fine with virtio-gpu. For example,
ChoromeOS wirh crosvm disables display entirely even on guest side by
building virtio-gpu kernel driver without KMS support. This is something
to improve in QEMU to make it work without GL context.

-- 
Best regards,
Dmitry

  parent reply	other threads:[~2026-09-07 13:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  3:19 About new backend for GPU compute ROCm in qemu Huang, Honglei
2026-08-17  9:06 ` Alex Bennée
2026-08-17 12:46   ` Huang, Honglei
2026-08-17 11:44 ` Akihiko Odaki
2026-08-17 13:44   ` Huang, Honglei
2026-08-17 14:24     ` Alex Bennée
2026-08-18  2:27       ` Huang, Honglei
2026-08-17 16:29     ` Akihiko Odaki
2026-08-18  2:50       ` Huang, Honglei
2026-08-18  4:05         ` Akihiko Odaki
2026-08-18  4:26           ` Huang, Honglei
2026-08-18  7:50             ` Akihiko Odaki
2026-08-18  8:53               ` Huang, Honglei
2026-08-18 11:27                 ` Akihiko Odaki
2026-08-19  2:37                   ` Huang, Honglei
2026-08-19  9:38                     ` Akihiko Odaki
2026-08-20 10:49                   ` Huang, Honglei
2026-09-07 13:12                     ` Dmitry Osipenko
2026-09-08  5:33                       ` Huang, Honglei
2026-09-07 13:05 ` Dmitry Osipenko [this message]
2026-09-08  5:37   ` Huang, Honglei

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=fc5c5bc5-d3a5-47f4-8a86-bcd531f0803c@collabora.com \
    --to=dmitry.osipenko@collabora.com \
    --cc=Ray.Huang@amd.com \
    --cc=airlied@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=honghuan@amd.com \
    --cc=honglei1.huang@amd.com \
    --cc=kraxel@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtualization@lists.linux.dev \
    /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