From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Akihiko Odaki" <akihiko.odaki@daynix.com>,
"Huang Rui" <ray.huang@amd.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Gert Wollny" <gert.wollny@collabora.com>,
qemu-devel@nongnu.org,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Alyssa Ross" <hi@alyssa.is>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Stefano Stabellini" <stefano.stabellini@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Xenia Ragiadakou" <xenia.ragiadakou@amd.com>,
"Pierre-Eric Pelloux-Prayer" <pierre-eric.pelloux-prayer@amd.com>,
"Honglei Huang" <honglei1.huang@amd.com>,
"Julia Zhang" <julia.zhang@amd.com>,
"Chen Jiqian" <Jiqian.Chen@amd.com>,
"Rob Clark" <robdclark@gmail.com>,
"Yiwei Zhang" <zzyiwei@chromium.org>,
"Sergio Lopez Pascual" <slp@redhat.com>
Subject: Re: [PATCH v4 0/5] Support virtio-gpu DRM native context
Date: Sun, 12 Jan 2025 19:46:56 +0300 [thread overview]
Message-ID: <307120fe-c950-42d0-a775-a64d847a3b00@collabora.com> (raw)
In-Reply-To: <874j24vwku.fsf@draig.linaro.org>
On 1/12/25 19:14, Alex Bennée wrote:
> So this goes away with:
>
> Linux draig 6.13.0-rc6-ajb-00144-g8c8d54116fa2-dirty #27 SMP PREEMPT_DYNAMIC Fri Jan 10 16:57:29 GMT 2025 x86_64 GNU/Linux
>
> So I think is an artefact of the PFN page locking failing. I guess
> native context is more prone to issues? It is a bit odd as I have loads
> of memory and I think the intel graphics are unified memory but I don't
> know how you would check.
Native context is about same prone as Venus. For Intel GFX it doesn't
matter much whether it's dGPU or iGPU. i915 driver would use huge pages
for UMA which is affected by the same KVM/PFN issue. In a case of UMA,
you may explicitly disable transparent huge pages to work around the
problem, but this is no necessary anymore using 6.13+ kernel. Glad it
was an easy fix!
--
Best regards,
Dmitry
next prev parent reply other threads:[~2025-01-12 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 22:18 [PATCH v4 0/5] Support virtio-gpu DRM native context Dmitry Osipenko
2024-11-10 22:18 ` [PATCH v4 1/5] ui/sdl2: Restore original context after new context creation Dmitry Osipenko
2024-11-10 22:18 ` [PATCH v4 2/5] ui/sdl2: Implement dpy dmabuf functions Dmitry Osipenko
2024-11-10 22:18 ` [PATCH v4 3/5] virtio-gpu: Handle virgl fence creation errors Dmitry Osipenko
2024-11-10 22:18 ` [PATCH v4 4/5] virtio-gpu: Support asynchronous fencing Dmitry Osipenko
2025-01-13 22:00 ` Alex Bennée
2025-01-14 12:19 ` Dmitry Osipenko
2024-11-10 22:18 ` [PATCH v4 5/5] virtio-gpu: Support DRM native context Dmitry Osipenko
2024-11-11 5:18 ` [PATCH v4 0/5] Support virtio-gpu " Akihiko Odaki
2025-01-08 13:14 ` Michael S. Tsirkin
2025-01-12 15:48 ` Dmitry Osipenko
2025-01-10 12:16 ` Alex Bennée
2025-01-12 15:49 ` Dmitry Osipenko
2025-01-10 13:38 ` Alex Bennée
2025-01-12 15:56 ` Dmitry Osipenko
2025-01-12 16:14 ` Alex Bennée
2025-01-12 16:46 ` Dmitry Osipenko [this message]
2025-01-12 17:05 ` Alex Bennée
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=307120fe-c950-42d0-a775-a64d847a3b00@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=Jiqian.Chen@amd.com \
--cc=akihiko.odaki@daynix.com \
--cc=alex.bennee@linaro.org \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.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=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=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 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).