From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Xen developer discussion" <xen-devel@lists.xenproject.org>,
amd-gfx@lists.freedesktop.org, christian.koenig@amd.com,
dri-devel@lists.freedesktop.org,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Subject: Re: AMD GPU problems under Xen
Date: Mon, 28 Nov 2022 20:59:28 -0500 [thread overview]
Message-ID: <Y4Vngz5tTA74Qr8L@itl-email> (raw)
In-Reply-To: <CADnq5_NfupG-DzNDJfntg+uSWH2m_8mLfj=ddkMdnNYNRhXWUw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2320 bytes --]
On Mon, Nov 28, 2022 at 11:18:00AM -0500, Alex Deucher wrote:
> On Mon, Nov 28, 2022 at 2:18 AM Demi Marie Obenour
> <demi@invisiblethingslab.com> wrote:
> >
> > Dear Christian:
> >
> > What is the status of the AMDGPU work for Xen dom0? That was mentioned in
> > https://lore.kernel.org/dri-devel/b2dec9b3-03a7-e7ac-306e-1da024af8982@amd.com/
> > and there have been bug reports to Qubes OS about problems with AMDGPU
> > under Xen (such as https://github.com/QubesOS/qubes-issues/issues/7648).
>
> I would say it's a work in progress. It depends what GPU you have
> and what type of xen setup you are using (PV vs PVH, etc.).
The current situation is:
- dom0 is PV.
- VMs with assigned PCI devices are HVM and use a Linux-based stubdomain
QEMU does not run in dom0.
- Everything else is PVH.
In the future, I believe the goal is to move away from PV and HVM in
favor of PVH, though HVM support will remain for compatibility with
guests (such as Windows) that need emulated devices.
> In general, your best bet currently is dGPU add in boards because they
> are largely self contained.
The main problem is that for the trusted GUI to work, there needs to
be at least one GPU attached to a trusted VM, such as the host or a
dedicated GUI VM. That VM will typically not be running graphics-
intensive workloads, so the compute power of a dGPU is largely wasted.
SR-IOV support would help with that, but the only GPU vendor with open
source SR-IOV support is Intel and it is still not upstream. I am also
not certain if the support extends to Arc dGPUs.
> APUs and platforms with integrated dGPUs
> are a bit more complicated as they tend to have more platform
> dependencies like ACPI tables and methods in order for the driver to
> be able to initialize the hardware properly.
Is Xen dom0/domU support for such GPUs being worked on? Is there an
estimate as to when the needed support will be available upstream? This
is mostly directed at Christian and other people who work for hardware
vendors.
> Additionally, GPUs map a
> lot of system memory so bounce buffers aren't really viable. You'll
> really need IOMMU,
Qubes OS already needs an IOMMU so that is not a concern.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-11-29 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 9:54 AMD GPU problems under Xen Demi Marie Obenour
2022-11-28 16:18 ` Alex Deucher
2022-11-29 1:59 ` Demi Marie Obenour [this message]
2022-11-29 14:32 ` Alex Deucher
2022-11-29 15:15 ` Marek Marczykowski-Górecki
2022-11-29 15:24 ` Alex Deucher
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=Y4Vngz5tTA74Qr8L@itl-email \
--to=demi@invisiblethingslab.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=marmarek@invisiblethingslab.com \
--cc=xen-devel@lists.xenproject.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