From: Thomas Zimmermann <tzimmermann@suse.de>
To: "José Expósito" <jose.exposito89@gmail.com>,
"Simona Vetter" <simona.vetter@ffwll.ch>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Jonathan.Cameron@huawei.com, airlied@gmail.com,
aleksander.lobakin@intel.com, andriy.shevchenko@linux.intel.com,
bhelgaas@google.com, broonie@kernel.org, dakr@kernel.org,
dri-devel@lists.freedesktop.org, hamohammed.sa@gmail.com,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, louis.chauvet@bootlin.com,
lukas@wunner.de, lyude@redhat.com,
maarten.lankhorst@linux.intel.com, mairacanal@riseup.net,
melissa.srw@gmail.com, mripard@kernel.org,
quic_zijuhu@quicinc.com, rafael@kernel.org, robin.murphy@arm.com,
rust-for-linux@vger.kernel.org, simona@ffwll.ch
Subject: Re: [PATCH v4 9/9] drm/vkms: convert to use faux_device
Date: Fri, 13 Jun 2025 10:15:05 +0200 [thread overview]
Message-ID: <fa5f9e9c-09f6-4f92-8f6d-4e057f9fc5a9@suse.de> (raw)
In-Reply-To: <Z9MT23hgX2c21xNA@fedora>
Hi
Am 13.03.25 um 18:20 schrieb José Expósito:
> On Thu, Mar 13, 2025 at 03:22:21PM +0100, Simona Vetter wrote:
>> On Wed, Mar 12, 2025 at 07:22:07AM +0100, Greg KH wrote:
>>> On Tue, Mar 11, 2025 at 06:20:53PM +0100, José Expósito wrote:
>>>> Hi everyone,
>>>>
>>>>> On Tue, Feb 25, 2025 at 02:51:40PM +0100, Louis Chauvet wrote:
>>>>>>
>>>>>> Le 25/02/2025 à 12:41, Thomas Zimmermann a écrit :
>>>>>>> Hi
>>>>>>>
>>>>>>> Am 10.02.25 um 15:37 schrieb Louis Chauvet:
>>>>>>>> On 10/02/25 - 13:30, Greg Kroah-Hartman wrote:
>>>>>>>>> The vkms driver does not need to create a platform device, as there is
>>>>>>>>> no real platform resources associated it, it only did so because it was
>>>>>>>>> simple to do that in order to get a device to use for resource
>>>>>>>>> management of drm resources. Change the driver to use the faux device
>>>>>>>>> instead as this is NOT a real platform device.
>>>>>>>>>
>>>>>>>>> Cc: Louis Chauvet <louis.chauvet@bootlin.com>
>>>>>>>>> Cc: Haneen Mohammed <hamohammed.sa@gmail.com>
>>>>>>>>> Cc: Simona Vetter <simona@ffwll.ch>
>>>>>>>>> Cc: Melissa Wen <melissa.srw@gmail.com>
>>>>>>>>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>>>>>>>>> Cc: Maxime Ripard <mripard@kernel.org>
>>>>>>>>> Cc: Thomas Zimmermann <tzimmermann@suse.de>
>>>>>>>>> Cc: David Airlie <airlied@gmail.com>
>>>>>>>>> Cc: dri-devel@lists.freedesktop.org
>>>>>>>>> Reviewed-by: Lyude Paul <lyude@redhat.com>
>>>>>>>>> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>>>>>> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
>>>>>>>
>>>>>>>> Tested-by: Louis Chauvet <louis.chauvet@bootlin.com>
>>>>>>>> Reviewed-by: Louis Chauvet <louis.chauvet@bootlin.com>
>>>>>>>>
>>>>>>>> Thanks for the modification, it seems to work.
>>>>>>> Should this patch be merged through DRM trees? drm-misc-next is at
>>>>>>> v6.14-rc4 and has struct faux_device.
>>>>>> Hi,
>>>>>>
>>>>>> I was not aware the faux-device was merged, as it is a new feature, I
>>>>>> expected it to reach drm-misc-next on 6.15-rc1.
>>>>> I added it to Linus's tree just so that DRM could get these changes into
>>>>> their tree now :)
>>>>>
>>>>>> I plan to merge [1] today/tomorrow (well tested with platform_device), and
>>>>>> then I will submit an updated version of this patch (only trivial conflicts,
>>>>>> but never tested with multiple VKMS devices).
>>>>>>
>>>>>> [1]:https://lore.kernel.org/all/20250218101214.5790-1-jose.exposito89@gmail.com/
>>>>> Great, thanks!
>>>>>
>>>>> greg k-h
>>>> Testing this patch again as part of some IGT tests I'm working on,
>>>> I noticed that, applying this patch on top of the latest drm-misc-next
>>>> triggers a warning at drivers/gpu/drm/drm_gem.c:571, in
>>>> drm_gem_get_pages():
>>>>
>>>> if (WARN_ON(!obj->filp))
>>>> return ERR_PTR(-EINVAL);
>>> I don't see how the faux bus change would have anything to do with a
>>> filp as that's not related as far as I can tell. But I don't know the
>>> drm layer at all, where does that filp come from?
>> Yeah that filp is the shmem file that backs gem bo. That's very far away
>> from anything device/driver related datastrctures. If this is a new
>> failure due to the aux bux conversion then it would be really surprising.
> Agreed, I find it surprising, but reverting the patch removes the warning.
>
> It's most likely an issue on my side, but I decided to double check just
> in case someone else is also seeing this warning.
Any news on this issue?
Best regards
Thomas
>
> Jose
>
>> -Sima
>>
>> --
>> Simona Vetter
>> Software Engineer, Intel Corporation
>> http://blog.ffwll.ch
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2025-06-13 8:15 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 12:30 [PATCH v4 0/9] Driver core: Add faux bus devices Greg Kroah-Hartman
2025-02-10 12:30 ` [PATCH v4 1/9] driver core: add a faux bus for use when a simple device/bus is needed Greg Kroah-Hartman
2025-02-10 14:29 ` Kurt Borja
2025-02-10 14:45 ` Greg Kroah-Hartman
2025-02-10 14:58 ` Kurt Borja
2025-02-10 15:36 ` Greg Kroah-Hartman
2025-02-10 15:52 ` Kurt Borja
2025-02-11 5:50 ` Greg Kroah-Hartman
2025-02-11 20:06 ` Lyude Paul
2025-02-11 21:57 ` Kurt Borja
2025-02-11 15:29 ` Zijun Hu
2025-02-11 15:49 ` Kurt Borja
2025-02-12 7:39 ` Greg Kroah-Hartman
2025-02-10 17:56 ` Kurt Borja
2025-02-11 7:27 ` Greg Kroah-Hartman
2025-02-11 7:33 ` Greg Kroah-Hartman
2025-02-11 7:43 ` Kurt Borja
2025-02-11 8:17 ` Greg Kroah-Hartman
2025-02-11 8:36 ` Kurt Borja
2025-02-11 2:49 ` Zijun Hu
2025-02-10 12:30 ` [PATCH v4 2/9] rust/kernel: Add faux device bindings Greg Kroah-Hartman
2025-02-10 16:32 ` Benno Lossin
2025-02-10 18:18 ` Danilo Krummrich
2025-02-11 5:52 ` Greg Kroah-Hartman
2025-02-10 18:41 ` Lyude Paul
2025-02-10 21:31 ` Danilo Krummrich
2025-02-12 14:58 ` Gary Guo
2025-02-10 12:30 ` [PATCH v4 3/9] regulator: dummy: convert to use the faux device interface Greg Kroah-Hartman
2025-02-10 12:30 ` [PATCH v4 4/9] x86/microcode: move away from using a fake platform device Greg Kroah-Hartman
2025-02-10 12:30 ` [PATCH v4 5/9] wifi: cfg80211: " Greg Kroah-Hartman
2025-02-10 12:30 ` [PATCH v4 6/9] tlclk: convert to use faux_device Greg Kroah-Hartman
2025-02-10 12:30 ` [PATCH v4 7/9] misc: lis3lv02d: " Greg Kroah-Hartman
2025-02-10 12:30 ` [PATCH v4 8/9] drm/vgem/vgem_drv " Greg Kroah-Hartman
2025-02-25 11:38 ` Thomas Zimmermann
2025-02-26 8:18 ` Thomas Zimmermann
2025-02-10 12:30 ` [PATCH v4 9/9] drm/vkms: " Greg Kroah-Hartman
2025-02-10 14:37 ` Louis Chauvet
2025-02-10 14:49 ` Greg Kroah-Hartman
2025-02-25 11:41 ` Thomas Zimmermann
2025-02-25 13:51 ` Louis Chauvet
2025-02-26 10:07 ` Greg Kroah-Hartman
2025-03-11 17:20 ` José Expósito
2025-03-11 17:24 ` José Expósito
2025-03-12 6:22 ` Greg KH
2025-03-13 14:22 ` Simona Vetter
2025-03-13 17:20 ` José Expósito
2025-06-13 8:15 ` Thomas Zimmermann [this message]
2025-06-13 11:55 ` José Expósito
2025-06-13 12:33 ` Thomas Zimmermann
2025-06-13 15:28 ` José Expósito
2025-06-13 15:39 ` Thomas Zimmermann
2025-02-27 13:06 ` [PATCH v4 0/9] Driver core: Add faux bus devices Louis Chauvet
2025-02-27 15:18 ` Andy Shevchenko
2025-02-27 15:30 ` Greg Kroah-Hartman
2025-02-28 10:38 ` Simona Vetter
2025-02-28 11:27 ` José Expósito
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=fa5f9e9c-09f6-4f92-8f6d-4e057f9fc5a9@suse.de \
--to=tzimmermann@suse.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=airlied@gmail.com \
--cc=aleksander.lobakin@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hamohammed.sa@gmail.com \
--cc=jose.exposito89@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=louis.chauvet@bootlin.com \
--cc=lukas@wunner.de \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mairacanal@riseup.net \
--cc=melissa.srw@gmail.com \
--cc=mripard@kernel.org \
--cc=quic_zijuhu@quicinc.com \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona.vetter@ffwll.ch \
--cc=simona@ffwll.ch \
/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).