From: "Alex Bennée" <alex.bennee@linaro.org>
To: liucong2565@phytium.com.cn
Cc: "Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
"Sean Christopherson" <seanjc@google.com>,
Jiqian.Chen@amd.com, akihiko.odaki@daynix.com,
alexander.deucher@amd.com, christian.koenig@amd.com,
gert.wollny@collabora.com, gurchetansingh@chromium.org,
hi@alyssa.is, honglei1.huang@amd.com, julia.zhang@amd.com,
kraxel@redhat.com, marcandre.lureau@redhat.com, mst@redhat.com,
pbonzini@redhat.com, philmd@linaro.org,
pierre-eric.pelloux-prayer@amd.com, qemu-devel@nongnu.org,
ray.huang@amd.com, robdclark@gmail.com, roger.pau@citrix.com,
slp@redhat.com, stefano.stabellini@amd.com,
xenia.ragiadakou@amd.com, zzyiwei@chromium.org
Subject: Re: [PATCH v11 04/10] virtio-gpu: Support asynchronous fencing
Date: Mon, 28 Apr 2025 14:55:35 +0100 [thread overview]
Message-ID: <87y0vk4ch4.fsf@draig.linaro.org> (raw)
In-Reply-To: <3118467e.dc3.1967c73dca7.Coremail.liucong2565@phytium.com.cn> (liucong's message of "Mon, 28 Apr 2025 20:51:30 +0800 (GMT+08:00)")
liucong2565@phytium.com.cn writes:
> I user Phytium D3000 8 Core, and I am not sure if it has a broken PCI.
>
> https://www.cpubenchmark.net/cpu.php?cpu=ARM+Phytium+D3000+8+Core+2500+MHz
Ahh - looks totally unrelated to the Altera platform so hopefully that
isn't an issue. Apparently a lot of the PCIe implementations are based
off the same underlying IP but without details its hard to check.
I assume everything runs fine directly when not virtualised? Without a
patched kernel on the AVA you would see corruption for X11 systems
(although not Wayland). e.g.:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9100
If you are happy your Arm can drive the AMD GPU ok from the host system
you should focus on verifying the page locking is working as intended
for the guests.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-04-28 13:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 12:05 [PATCH v11 00/10] Support virtio-gpu DRM native context Dmitry Osipenko
2025-03-10 12:05 ` [PATCH v11 01/10] ui/sdl2: Restore original context after new context creation Dmitry Osipenko
2025-03-10 12:05 ` [PATCH v11 02/10] ui/sdl2: Implement dpy dmabuf functions Dmitry Osipenko
2025-03-10 12:05 ` [PATCH v11 03/10] virtio-gpu: Handle virgl fence creation errors Dmitry Osipenko
2025-03-10 12:05 ` [PATCH v11 04/10] virtio-gpu: Support asynchronous fencing Dmitry Osipenko
2025-04-10 9:54 ` Cong Liu
2025-04-10 21:59 ` Dmitry Osipenko
2025-04-11 1:42 ` 刘聪
2025-04-14 14:47 ` Dmitry Osipenko
2025-04-26 22:27 ` Dmitry Osipenko
2025-04-27 11:53 ` 刘聪
2025-04-27 12:54 ` Alex Bennée
2025-04-28 14:38 ` Sean Christopherson
2025-04-27 14:16 ` Dmitry Osipenko
2025-04-28 10:07 ` Alex Bennée
2025-04-28 12:51 ` liucong2565
2025-04-28 13:55 ` Alex Bennée [this message]
2025-03-10 12:05 ` [PATCH v11 05/10] virtio-gpu: Support DRM native context Dmitry Osipenko
2025-03-10 12:05 ` [PATCH v11 06/10] ui/sdl2: Don't disable scanout when display is refreshed Dmitry Osipenko
2025-03-10 12:05 ` [PATCH v11 07/10] ui/gtk: " Dmitry Osipenko
2025-03-10 12:05 ` [PATCH v11 08/10] docs/system: virtio-gpu: Add link to Mesa VirGL doc Dmitry Osipenko
2025-03-10 12:05 ` [PATCH v11 09/10] docs/system: virtio-gpu: Update Venus link Dmitry Osipenko
2025-03-10 12:05 ` [PATCH v11 10/10] docs/system: virtio-gpu: Document host/guest requirements Dmitry Osipenko
2025-03-10 12:25 ` Akihiko Odaki
2025-03-10 12:29 ` Dmitry Osipenko
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=87y0vk4ch4.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=Jiqian.Chen@amd.com \
--cc=akihiko.odaki@daynix.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=dmitry.osipenko@collabora.com \
--cc=gert.wollny@collabora.com \
--cc=gurchetansingh@chromium.org \
--cc=hi@alyssa.is \
--cc=honglei1.huang@amd.com \
--cc=julia.zhang@amd.com \
--cc=kraxel@redhat.com \
--cc=liucong2565@phytium.com.cn \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=qemu-devel@nongnu.org \
--cc=ray.huang@amd.com \
--cc=robdclark@gmail.com \
--cc=roger.pau@citrix.com \
--cc=seanjc@google.com \
--cc=slp@redhat.com \
--cc=stefano.stabellini@amd.com \
--cc=xenia.ragiadakou@amd.com \
--cc=zzyiwei@chromium.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.