From: Thomas Zimmermann <tzimmermann@suse.de>
To: Alex Williamson <alex.williamson@redhat.com>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
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: Re: [PATCH 2/2] vfio/pci: Remove console drivers
Date: Wed, 8 Jun 2022 13:11:21 +0200 [thread overview]
Message-ID: <0c45183c-cdb8-4578-e346-bc4855be038f@suse.de> (raw)
In-Reply-To: <165453800875.3592816.12944011921352366695.stgit@omen>
[-- Attachment #1.1: Type: text/plain, Size: 3433 bytes --]
Hi Alex
Am 06.06.22 um 19:53 schrieb Alex Williamson:
> Console drivers can create conflicts with PCI resources resulting in
> userspace getting mmap failures to memory BARs. This is especially evident
> when trying to re-use the system primary console for userspace drivers.
> Attempt to remove all nature of conflicting drivers as part of our VGA
> initialization.
First a dumb question about your use case. You want to assign a PCI
graphics card to a virtual machine and need to remove the generic driver
from the framebuffer?
>
> Reported-by: Laszlo Ersek <lersek@redhat.com>
> Tested-by: Laszlo Ersek <lersek@redhat.com>
> Suggested-by: Gerd Hoffmann <kraxel@redhat.com>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
> drivers/vfio/pci/vfio_pci_core.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/drivers/vfio/pci/vfio_pci_core.c b/drivers/vfio/pci/vfio_pci_core.c
> index a0d69ddaf90d..e0cbcbc2aee1 100644
> --- a/drivers/vfio/pci/vfio_pci_core.c
> +++ b/drivers/vfio/pci/vfio_pci_core.c
> @@ -13,6 +13,7 @@
> #include <linux/device.h>
> #include <linux/eventfd.h>
> #include <linux/file.h>
> +#include <linux/fb.h>
> #include <linux/interrupt.h>
> #include <linux/iommu.h>
> #include <linux/module.h>
> @@ -29,6 +30,8 @@
>
> #include <linux/vfio_pci_core.h>
>
> +#include <drm/drm_aperture.h>
> +
> #define DRIVER_AUTHOR "Alex Williamson <alex.williamson@redhat.com>"
> #define DRIVER_DESC "core driver for VFIO based PCI devices"
>
> @@ -1793,6 +1796,20 @@ static int vfio_pci_vga_init(struct vfio_pci_core_device *vdev)
> if (!vfio_pci_is_vga(pdev))
> return 0;
>
> +#if IS_REACHABLE(CONFIG_DRM)
> + drm_aperture_detach_platform_drivers(pdev);
> +#endif
> +
> +#if IS_REACHABLE(CONFIG_FB)
> + ret = remove_conflicting_pci_framebuffers(pdev, vdev->vdev.ops->name);
> + if (ret)
> + return ret;
> +#endif
> +
> + ret = vga_remove_vgacon(pdev);
> + if (ret)
> + return ret;
> +
You shouldn't have to copy any of the implementation of the aperture
helpers.
If you call drm_aperture_remove_conflicting_pci_framebuffers() it should
work correctly. The only reason why it requires a DRM driver structure
as second argument is for the driver's name. [1] And that name is only
used for printing an info message. [2]
The plan forward would be to drop patch 1 entirely.
For patch 2, the most trivial workaround is to instanciate struct
drm_driver here and set the name field to 'vdev->vdev.ops->name'. In the
longer term, the aperture helpers will be moved out of DRM and into a
more prominent location. That workaround will be cleaned up then.
Alternatively, drm_aperture_remove_conflicting_pci_framebuffers() could
be changed to accept the name string as second argument, but that's
quite a bit of churn within the DRM code.
Best regards
Thomas
[1]
https://elixir.bootlin.com/linux/v5.18.2/source/drivers/gpu/drm/drm_aperture.c#L347
[2]
https://elixir.bootlin.com/linux/v5.18.2/source/drivers/video/fbdev/core/fbmem.c#L1570
> ret = vga_client_register(pdev, vfio_pci_set_decode);
> if (ret)
> return ret;
>
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-06-08 11:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` [PATCH 2/2] vfio/pci: Remove console drivers Alex Williamson
2022-06-08 11:11 ` Thomas Zimmermann [this message]
2022-06-08 14:04 ` Alex Williamson
2022-06-09 9:13 ` Thomas Zimmermann
2022-06-09 21:41 ` 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-07 17:40 ` [PATCH 0/2] Improve vfio-pci primary GPU assignment behavior Javier Martinez Canillas
2022-06-07 21:01 ` Alex Williamson
2022-06-08 7:43 ` Gerd Hoffmann
2022-06-08 8:51 ` Javier Martinez Canillas
2022-06-08 9:11 ` Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2022-12-04 0:12 [PATCH 2/2] vfio/pci: Remove console drivers mb
2022-12-05 0:51 ` Alex Williamson
2022-12-05 9:00 ` Thomas Zimmermann
[not found] ` <CAEdEoBYZa9cg0nq=P7EDsDS9m2EKYrd8M8ucqi8U0Csj0mtjDg@mail.gmail.com>
2022-12-05 10:11 ` Thomas Zimmermann
2022-12-05 21:50 ` mb
2023-01-02 10:33 ` Shawn Michaels
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=0c45183c-cdb8-4578-e346-bc4855be038f@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=alex.williamson@redhat.com \
--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 \
/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