From: Gerd Hoffmann <kraxel@redhat.com> To: Thomas Zimmermann <tzimmermann@suse.de> Cc: Alex Williamson <alex.williamson@redhat.com>, maarten.lankhorst@linux.intel.com, mripard@kernel.org, airlied@linux.ie, daniel@ffwll.ch, kvm@vger.kernel.org, Laszlo Ersek <lersek@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 17:37:47 +0200 [thread overview] Message-ID: <20220608153747.5d5h446vzbteqzwb@sirius.home.kraxel.org> (raw) In-Reply-To: <0c45183c-cdb8-4578-e346-bc4855be038f@suse.de> Hi, > You shouldn't have to copy any of the implementation of the aperture > helpers. That comes from the aperture helpers being part of drm ... > 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. ... but if the long-term plan is to clean that up properly anyway I don't see the point in bike shedding too much on the details of some temporary solution. > 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. Also pointless churn because you'll have the very same churn again when moving the aperture helpers out of drm. take care, Gerd
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com> To: Thomas Zimmermann <tzimmermann@suse.de> Cc: kvm@vger.kernel.org, airlied@linux.ie, linux-kernel@vger.kernel.org, Alex Williamson <alex.williamson@redhat.com>, dri-devel@lists.freedesktop.org, Laszlo Ersek <lersek@redhat.com> Subject: Re: [PATCH 2/2] vfio/pci: Remove console drivers Date: Wed, 8 Jun 2022 17:37:47 +0200 [thread overview] Message-ID: <20220608153747.5d5h446vzbteqzwb@sirius.home.kraxel.org> (raw) In-Reply-To: <0c45183c-cdb8-4578-e346-bc4855be038f@suse.de> Hi, > You shouldn't have to copy any of the implementation of the aperture > helpers. That comes from the aperture helpers being part of drm ... > 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. ... but if the long-term plan is to clean that up properly anyway I don't see the point in bike shedding too much on the details of some temporary solution. > 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. Also pointless churn because you'll have the very same churn again when moving the aperture helpers out of drm. take care, Gerd
next prev parent reply other threads:[~2022-06-08 15:38 UTC|newest] Thread overview: 39+ 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 ` 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 [this message] 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 2022-12-04 0:12 [PATCH 2/2] vfio/pci: Remove console drivers mb 2022-12-04 0:12 ` mb 2022-12-05 0:51 ` Alex Williamson 2022-12-05 0:51 ` Alex Williamson 2022-12-05 9:00 ` Thomas Zimmermann 2022-12-05 9:32 ` mb 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=20220608153747.5d5h446vzbteqzwb@sirius.home.kraxel.org \ --to=kraxel@redhat.com \ --cc=airlied@linux.ie \ --cc=alex.williamson@redhat.com \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --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.