From: Alex Williamson <alex.williamson@redhat.com> To: maarten.lankhorst@linux.intel.com, mripard@kernel.org, tzimmermann@suse.de, airlied@linux.ie, daniel@ffwll.ch Cc: Laszlo Ersek <lersek@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org Subject: [PATCH 0/2] Improve vfio-pci primary GPU assignment behavior Date: Mon, 06 Jun 2022 11:53:15 -0600 [thread overview] Message-ID: <165453797543.3592816.6381793341352595461.stgit@omen> (raw) Users attempting to enable vfio PCI device assignment with a GPU will often block the default PCI driver from the device to avoid conflicts with the device initialization or release path. This means that vfio-pci is sometimes the first PCI driver to bind to the device. In the case of assigning the primary graphics device, low-level console drivers may still generate resource conflicts. Users often employ kernel command line arguments to disable conflicting drivers or perform unbinding in userspace to avoid this, but the actual solution is often distribution/kernel config specific based on the included drivers. We can instead allow vfio-pci to copy the behavior of drm_aperture_remove_conflicting_pci_framebuffers() in order to remove these low-level drivers with conflicting resources. vfio-pci is not however a DRM driver, nor does vfio-pci depend on DRM config options, thus we split out and export the necessary DRM apterture support and mirror the framebuffer and VGA support. I'd be happy to pull this series in through the vfio branch if approved by the DRM maintainers. Thanks, Alex --- Alex Williamson (2): drm/aperture: Split conflicting platform driver removal vfio/pci: Remove console drivers drivers/gpu/drm/drm_aperture.c | 33 +++++++++++++++++++++++--------- drivers/vfio/pci/vfio_pci_core.c | 17 ++++++++++++++++ include/drm/drm_aperture.h | 2 ++ 3 files changed, 43 insertions(+), 9 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson@redhat.com> To: maarten.lankhorst@linux.intel.com, mripard@kernel.org, tzimmermann@suse.de, airlied@linux.ie, daniel@ffwll.ch Cc: kvm@vger.kernel.org, Laszlo Ersek <lersek@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/2] Improve vfio-pci primary GPU assignment behavior Date: Mon, 06 Jun 2022 11:53:15 -0600 [thread overview] Message-ID: <165453797543.3592816.6381793341352595461.stgit@omen> (raw) Users attempting to enable vfio PCI device assignment with a GPU will often block the default PCI driver from the device to avoid conflicts with the device initialization or release path. This means that vfio-pci is sometimes the first PCI driver to bind to the device. In the case of assigning the primary graphics device, low-level console drivers may still generate resource conflicts. Users often employ kernel command line arguments to disable conflicting drivers or perform unbinding in userspace to avoid this, but the actual solution is often distribution/kernel config specific based on the included drivers. We can instead allow vfio-pci to copy the behavior of drm_aperture_remove_conflicting_pci_framebuffers() in order to remove these low-level drivers with conflicting resources. vfio-pci is not however a DRM driver, nor does vfio-pci depend on DRM config options, thus we split out and export the necessary DRM apterture support and mirror the framebuffer and VGA support. I'd be happy to pull this series in through the vfio branch if approved by the DRM maintainers. Thanks, Alex --- Alex Williamson (2): drm/aperture: Split conflicting platform driver removal vfio/pci: Remove console drivers drivers/gpu/drm/drm_aperture.c | 33 +++++++++++++++++++++++--------- drivers/vfio/pci/vfio_pci_core.c | 17 ++++++++++++++++ include/drm/drm_aperture.h | 2 ++ 3 files changed, 43 insertions(+), 9 deletions(-)
next reply other threads:[~2022-06-06 17:53 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-06 17:53 Alex Williamson [this message] 2022-06-06 17:53 ` [PATCH 0/2] Improve vfio-pci primary GPU assignment behavior Alex Williamson 2022-06-06 17:53 ` [PATCH 1/2] drm/aperture: Split conflicting platform driver removal Alex Williamson 2022-06-06 17:53 ` Alex Williamson 2022-06-06 17:53 ` [PATCH 2/2] vfio/pci: Remove console drivers Alex Williamson 2022-06-06 17:53 ` Alex Williamson 2022-06-08 11:11 ` Thomas Zimmermann 2022-06-08 11:11 ` Thomas Zimmermann 2022-06-08 14:04 ` Alex Williamson 2022-06-08 14:04 ` Alex Williamson 2022-06-09 9:13 ` Thomas Zimmermann 2022-06-09 9:13 ` Thomas Zimmermann 2022-06-09 21:41 ` Alex Williamson 2022-06-09 21:41 ` Alex Williamson 2022-06-09 21:44 ` Alex Williamson 2022-06-09 21:44 ` Alex Williamson 2022-06-10 7:03 ` Thomas Zimmermann 2022-06-10 14:30 ` Alex Williamson 2022-06-08 15:37 ` Gerd Hoffmann 2022-06-08 15:37 ` Gerd Hoffmann 2022-06-07 17:40 ` [PATCH 0/2] Improve vfio-pci primary GPU assignment behavior Javier Martinez Canillas 2022-06-07 17:40 ` Javier Martinez Canillas 2022-06-07 21:01 ` Alex Williamson 2022-06-07 21:01 ` Alex Williamson 2022-06-08 7:43 ` Gerd Hoffmann 2022-06-08 7:43 ` Gerd Hoffmann 2022-06-08 8:51 ` Javier Martinez Canillas 2022-06-08 8:51 ` Javier Martinez Canillas 2022-06-08 9:11 ` Gerd Hoffmann 2022-06-08 9:11 ` Gerd Hoffmann
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=165453797543.3592816.6381793341352595461.stgit@omen \ --to=alex.williamson@redhat.com \ --cc=airlied@linux.ie \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=kraxel@redhat.com \ --cc=kvm@vger.kernel.org \ --cc=lersek@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=maarten.lankhorst@linux.intel.com \ --cc=mripard@kernel.org \ --cc=tzimmermann@suse.de \ /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: linkBe 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.