From: Emil Velikov <emil.l.velikov@gmail.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Gerd Hoffmann <kraxel@redhat.com>,
ML dri-devel <dri-devel@lists.freedesktop.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH 3/4] drm/virtio: remove drm_dev_set_unique workaround
Date: Wed, 28 Mar 2018 15:35:12 +0100 [thread overview]
Message-ID: <CACvgo505ZrxdzUdL+yHagdsiDPYB_aBfL=pGyOQ70YoXqD_mhw@mail.gmail.com> (raw)
In-Reply-To: <4b461dc5-5bff-af82-2716-7228b5f16d76@redhat.com>
Hi Laszlo,
On 28 March 2018 at 11:27, Laszlo Ersek <lersek@redhat.com> wrote:
> On 03/28/18 03:24, Emil Velikov wrote:
>> From: Emil Velikov <emil.velikov@collabora.com>
>>
>> Ealier commit a325725633c26aa66ab940f762a6b0778edf76c0 did not attribute
>> that virtio can be either PCI or a platform device and removed the
>> .set_busid hook. Whereas only the "platform" instance should have been
>> removed.
>>
>> Since then, two things have happened:
>> - the driver manually calls drm_dev_set_unique, addressing the Xserver
>> regression - see commit 9785b4321b0bd701f8d21d3d3c676a7739a5cf22
>> - core itself calls drm_pci_set_busid, on drm_set_busid IOCTL setting
>> the busid, so we don't need to fallback to dev->unique - see commit
>> 5c484cee7ef9c4fd29fa0ba09640d55960977145
>>
>> With that in place we can remove the local workaround.
>>
>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>> Cc: Gerd Hoffmann <kraxel@redhat.com>
>> Cc: Hans de Goede <hdegoede@redhat.com>
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
>> ---
>> Gents, can someone double-check this please? Just in case.
>
> I guess I should test whether this series regresses the use case
> described in c2cbc38b97; is that correct?
>
Precisely.
> I can add that to my todo list, but it won't be quick. I get into
> building kernels maybe once per quarter :)
>
> What repo and branch should I apply this series on top of? ... Actually,
> I was only CC'd on patch 3/4, so I don't even have the full series. Do
> you have a public branch somewhere?
>
In practise only 3/4 is needed applied on top of any tree that has the
commits mentioned in the summary.
FWIW here is a patchwork series [1], just this patch [2] and a tree [3].
[1] https://patchwork.freedesktop.org/series/40778/
[2] https://patchwork.freedesktop.org/patch/213335/
[3] https://github.com/evelikov/linux/commits/ioctl-cleanups
> (If this would mean too much work for you, esp. considering that I'm
> going to be slow, feel free to go ahead with the patch. Should I find
> later that something broke, I'll whine then. :) )
>
The original patch that caused breakage was tested, yet seemingly in a
different manner.
Hence, I'd love it, if anyone who had the original problem can can
give this a try.
I guess it can wait 1-2 weeks before getting merged, since it won't
cause any conflicts ;-)
Thanks!
Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-03-28 14:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 1:24 [PATCH 1/4] drm/vgem: Fix vgem_init to get drm device avaliable Emil Velikov
2018-03-28 1:24 ` [PATCH 2/4] drm: BUG_ON if passing NULL parent to drm_dev_init Emil Velikov
2018-03-28 7:17 ` Daniel Vetter
2018-03-28 1:24 ` [PATCH 3/4] drm/virtio: remove drm_dev_set_unique workaround Emil Velikov
2018-03-28 7:18 ` Daniel Vetter
2018-03-28 10:27 ` Laszlo Ersek
2018-03-28 14:35 ` Emil Velikov [this message]
2018-03-29 11:17 ` Laszlo Ersek
2018-04-03 17:13 ` Emil Velikov
2018-04-04 17:29 ` Laszlo Ersek
2018-04-06 12:15 ` Laszlo Ersek
2018-04-06 12:56 ` Emil Velikov
2018-04-09 8:26 ` Daniel Vetter
2018-04-09 10:24 ` Emil Velikov
2018-04-09 11:25 ` Emil Velikov
2018-04-13 15:45 ` Daniel Vetter
2018-04-06 13:06 ` Gerd Hoffmann
2018-03-28 1:24 ` [PATCH 4/4] drm: drm_dev_set_unique private, again Emil Velikov
2018-03-28 7:18 ` Daniel Vetter
2018-03-28 7:16 ` [PATCH 1/4] drm/vgem: Fix vgem_init to get drm device avaliable Daniel Vetter
2018-03-28 14:45 ` Emil Velikov
2018-03-28 14:49 ` Chris Wilson
2018-03-28 15:11 ` Emil Velikov
2018-03-29 7:17 ` Daniel Vetter
2018-04-04 10:46 ` Emil Velikov
2018-04-04 12:07 ` Daniel Vetter
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='CACvgo505ZrxdzUdL+yHagdsiDPYB_aBfL=pGyOQ70YoXqD_mhw@mail.gmail.com' \
--to=emil.l.velikov@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).