summaryrefslogtreecommitdiffstats
path: root/drivers/fpga/dfl-fme.h
diff options
context:
space:
mode:
authorMarek Marczykowski-Górecki <marmarek@invisiblethingslab.com>2022-04-27 01:57:15 +0200
committerAlex Deucher <alexander.deucher@amd.com>2022-05-04 18:20:14 +0200
commit19965d8259fdabc6806da92adda49684f5bcbec5 (patch)
tree8210cdd955e21935510da516e657d3b82132025d /drivers/fpga/dfl-fme.h
parentMerge tag 'amd-drm-fixes-5.18-2022-04-27' of https://gitlab.freedesktop.org/a... (diff)
downloadlinux-19965d8259fdabc6806da92adda49684f5bcbec5.tar.xz
linux-19965d8259fdabc6806da92adda49684f5bcbec5.zip
drm/amdgpu: do not use passthrough mode in Xen dom0
While technically Xen dom0 is a virtual machine too, it does have access to most of the hardware so it doesn't need to be considered a "passthrough". Commit b818a5d37454 ("drm/amdgpu/gmc: use PCI BARs for APUs in passthrough") changed how FB is accessed based on passthrough mode. This breaks amdgpu in Xen dom0 with message like this: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3 While the reason for this failure is unclear, the passthrough mode is not really necessary in Xen dom0 anyway. So, to unbreak booting affected kernels, disable passthrough mode in this case. Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1985 Fixes: b818a5d37454 ("drm/amdgpu/gmc: use PCI BARs for APUs in passthrough") Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Cc: stable@vger.kernel.org
Diffstat (limited to 'drivers/fpga/dfl-fme.h')
0 files changed, 0 insertions, 0 deletions