[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v4 0/5] Support virtio-gpu DRM native context
From: |
Alex Bennée |
Subject: |
Re: [PATCH v4 0/5] Support virtio-gpu DRM native context |
Date: |
Sun, 12 Jan 2025 17:05:23 +0000 |
User-agent: |
mu4e 1.12.8; emacs 29.4 |
Dmitry Osipenko <dmitry.osipenko@collabora.com> writes:
> 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!
I still can't get vulkaninfo to see anything (Error
vk::Instance:enumeratePhysicalDevices: ErrorInitializationFailed).
I've got your mesa native-context-iris set up with VK_ICD_FILENAMES
pointing at the virtio_icd.x86_64.json
VK_LOADER_DEBUG=1 doesn't show anything
--
Alex Bennée
Virtualisation Tech Lead @ Linaro