From: Mikko Perttunen <cyndis@kapsi.fi> To: Mikko Perttunen <mperttunen@nvidia.com>, Dmitry Osipenko <digetx@gmail.com>, Thierry Reding <thierry.reding@gmail.com> Cc: jonathanh@nvidia.com, airlied@linux.ie, daniel@ffwll.ch, linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org, talho@nvidia.com, bhuntsman@nvidia.com Subject: Re: [PATCH v5 01/21] gpu: host1x: Use different lock classes for each client Date: Fri, 26 Mar 2021 16:54:55 +0200 [thread overview] Message-ID: <0fb1b458-66bb-c9d8-04c7-174165b39811@kapsi.fi> (raw) In-Reply-To: <645366c2-c500-efcc-f44c-b933f6f470c4@nvidia.com> On 3/22/21 5:19 PM, Mikko Perttunen wrote: > On 22.3.2021 16.48, Dmitry Osipenko wrote: >> 22.03.2021 17:46, Thierry Reding пишет: >>> On Mon, Jan 11, 2021 at 02:59:59PM +0200, Mikko Perttunen wrote: >>>> To avoid false lockdep warnings, give each client lock a different >>>> lock class, passed from the initialization site by macro. >>>> >>>> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com> >>>> --- >>>> drivers/gpu/host1x/bus.c | 7 ++++--- >>>> include/linux/host1x.h | 9 ++++++++- >>>> 2 files changed, 12 insertions(+), 4 deletions(-) >>>> >>>> diff --git a/drivers/gpu/host1x/bus.c b/drivers/gpu/host1x/bus.c >>>> index 347fb962b6c9..8fc79e9cb652 100644 >>>> --- a/drivers/gpu/host1x/bus.c >>>> +++ b/drivers/gpu/host1x/bus.c >>>> @@ -715,13 +715,14 @@ EXPORT_SYMBOL(host1x_driver_unregister); >>>> * device and call host1x_device_init(), which will in turn call >>>> each client's >>>> * &host1x_client_ops.init implementation. >>>> */ >>>> -int host1x_client_register(struct host1x_client *client) >>>> +int __host1x_client_register(struct host1x_client *client, >>>> + struct lock_class_key *key) >>> >>> I've seen the kbuild robot warn about this because the kerneldoc is now >>> out of date. >>> >>>> { >>>> struct host1x *host1x; >>>> int err; >>>> INIT_LIST_HEAD(&client->list); >>>> - mutex_init(&client->lock); >>>> + __mutex_init(&client->lock, "host1x client lock", key); >>> >>> Should we maybe attempt to make this unique? Could we use something like >>> dev_name(client->dev) for this? >> >> I'm curious who the lockdep warning could be triggered at all, I don't >> recall ever seeing it. Mikko, could you please clarify how to reproduce >> the warning? >> > > This is pretty difficult to read but I guess it's some interaction > related to the delayed initialization of host1x clients? In any case, I > consistently get it at boot (though it may be triggered by vic probe > instead of nvdec). > > I'll fix the kbuild robot warnings and see if I can add a > client-specific lock name for v6. Lockdep doesn't seem to be liking dev_name() for the name, and I think allocating a string for this purpose seems a bit overkill, so I'll keep the lock name as is if there are no objections. Mikko > > Mikko > > [ 38.128257] WARNING: possible recursive locking detected > [ 38.133567] 5.11.0-rc2-next-20210108+ #102 Tainted: G S > [ 38.140089] -------------------------------------------- > [ 38.145395] systemd-udevd/239 is trying to acquire lock: > [ 38.150703] ffff0000997aa218 (&client->lock){+.+.}-{3:3}, at: > host1x_client_resume+0x30/0x100 [host1x] > [ 38.160142] > [ 38.160142] but task is already holding lock: > [ 38.165968] ffff000080c3b148 (&client->lock){+.+.}-{3:3}, at: > host1x_client_resume+0x30/0x100 [host1x] > [ 38.175398] > [ 38.175398] other info that might help us debug this: > [ 38.181918] Possible unsafe locking scenario: > [ 38.181918] > [ 38.187830] CPU0 > [ 38.190275] ---- > [ 38.192719] lock(&client->lock); > [ 38.196129] lock(&client->lock); > [ 38.199537] > [ 38.199537] *** DEADLOCK *** > [ 38.199537] > [ 38.205449] May be due to missing lock nesting notation > [ 38.205449] > [ 38.212228] 6 locks held by systemd-udevd/239: > [ 38.216669] #0: ffff00009261c188 (&dev->mutex){....}-{3:3}, at: > device_driver_attach+0x60/0x130 > [ 38.225487] #1: ffff800009a17168 (devices_lock){+.+.}-{3:3}, at: > host1x_client_register+0x7c/0x220 [host1x] > [ 38.235441] #2: ffff000083f94bb8 (&host->devices_lock){+.+.}-{3:3}, > at: host1x_client_register+0xac/0x220 [host1x] > [ 38.245996] #3: ffff0000a2267190 (&dev->mutex){....}-{3:3}, at: > __device_attach+0x8c/0x230 > [ 38.254372] #4: ffff000092c880f0 (&wgrp->lock){+.+.}-{3:3}, at: > tegra_display_hub_prepare+0xd8/0x170 [tegra_drm] > [ 38.264788] #5: ffff000080c3b148 (&client->lock){+.+.}-{3:3}, at: > host1x_client_resume+0x30/0x100 [host1x] > [ 38.274658] > [ 38.274658] stack backtrace: > [ 38.279012] CPU: 0 PID: 239 Comm: systemd-udevd Tainted: G S > 5.11.0-rc2-next-20210108+ #102 > [ 38.288660] Hardware name: NVIDIA Jetson TX2 Developer Kit (DT) > [ 38.294577] Call trace: > [ 38.297022] dump_backtrace+0x0/0x2c0 > [ 38.300695] show_stack+0x18/0x6c > [ 38.304013] dump_stack+0x120/0x19c > [ 38.307507] __lock_acquire+0x171c/0x2c34 > [ 38.311521] lock_acquire.part.0+0x230/0x490 > [ 38.315793] lock_acquire+0x70/0x90 > [ 38.319285] __mutex_lock+0x11c/0x6d0 > [ 38.322952] mutex_lock_nested+0x58/0x90 > [ 38.326877] host1x_client_resume+0x30/0x100 [host1x] > [ 38.332047] host1x_client_resume+0x44/0x100 [host1x] > [ 38.337200] tegra_display_hub_prepare+0xf8/0x170 [tegra_drm] > [ 38.343084] host1x_drm_probe+0x1fc/0x4f0 [tegra_drm] > [ 38.348256] host1x_device_probe+0x3c/0x50 [host1x] > [ 38.353240] really_probe+0x148/0x6f0 > [ 38.356906] driver_probe_device+0x78/0xe4 > [ 38.361005] __device_attach_driver+0x10c/0x170 > [ 38.365536] bus_for_each_drv+0xf0/0x160 > [ 38.369461] __device_attach+0x168/0x230 > [ 38.373385] device_initial_probe+0x14/0x20 > [ 38.377571] bus_probe_device+0xec/0x100 > [ 38.381494] device_add+0x580/0xbcc > [ 38.384985] host1x_subdev_register+0x178/0x1cc [host1x] > [ 38.390397] host1x_client_register+0x138/0x220 [host1x] > [ 38.395808] nvdec_probe+0x240/0x3ec [tegra_drm] > [ 38.400549] platform_probe+0x8c/0x110 > [ 38.404302] really_probe+0x148/0x6f0 > [ 38.407966] driver_probe_device+0x78/0xe4 > [ 38.412065] device_driver_attach+0x120/0x130 > [ 38.416423] __driver_attach+0xb4/0x190 > [ 38.420261] bus_for_each_dev+0xe8/0x160 > [ 38.424185] driver_attach+0x34/0x44 > [ 38.427761] bus_add_driver+0x1a4/0x2b0 > [ 38.431598] driver_register+0xe0/0x210 > [ 38.435437] __platform_register_drivers+0x6c/0x104 > [ 38.440318] host1x_drm_init+0x54/0x1000 [tegra_drm] > [ 38.445405] do_one_initcall+0xec/0x5e0 > [ 38.449244] do_init_module+0xe0/0x384 > [ 38.453000] load_module+0x32d8/0x3c60
WARNING: multiple messages have this Message-ID (diff)
From: Mikko Perttunen <cyndis@kapsi.fi> To: Mikko Perttunen <mperttunen@nvidia.com>, Dmitry Osipenko <digetx@gmail.com>, Thierry Reding <thierry.reding@gmail.com> Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org, jonathanh@nvidia.com, talho@nvidia.com, bhuntsman@nvidia.com, linux-tegra@vger.kernel.org Subject: Re: [PATCH v5 01/21] gpu: host1x: Use different lock classes for each client Date: Fri, 26 Mar 2021 16:54:55 +0200 [thread overview] Message-ID: <0fb1b458-66bb-c9d8-04c7-174165b39811@kapsi.fi> (raw) In-Reply-To: <645366c2-c500-efcc-f44c-b933f6f470c4@nvidia.com> On 3/22/21 5:19 PM, Mikko Perttunen wrote: > On 22.3.2021 16.48, Dmitry Osipenko wrote: >> 22.03.2021 17:46, Thierry Reding пишет: >>> On Mon, Jan 11, 2021 at 02:59:59PM +0200, Mikko Perttunen wrote: >>>> To avoid false lockdep warnings, give each client lock a different >>>> lock class, passed from the initialization site by macro. >>>> >>>> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com> >>>> --- >>>> drivers/gpu/host1x/bus.c | 7 ++++--- >>>> include/linux/host1x.h | 9 ++++++++- >>>> 2 files changed, 12 insertions(+), 4 deletions(-) >>>> >>>> diff --git a/drivers/gpu/host1x/bus.c b/drivers/gpu/host1x/bus.c >>>> index 347fb962b6c9..8fc79e9cb652 100644 >>>> --- a/drivers/gpu/host1x/bus.c >>>> +++ b/drivers/gpu/host1x/bus.c >>>> @@ -715,13 +715,14 @@ EXPORT_SYMBOL(host1x_driver_unregister); >>>> * device and call host1x_device_init(), which will in turn call >>>> each client's >>>> * &host1x_client_ops.init implementation. >>>> */ >>>> -int host1x_client_register(struct host1x_client *client) >>>> +int __host1x_client_register(struct host1x_client *client, >>>> + struct lock_class_key *key) >>> >>> I've seen the kbuild robot warn about this because the kerneldoc is now >>> out of date. >>> >>>> { >>>> struct host1x *host1x; >>>> int err; >>>> INIT_LIST_HEAD(&client->list); >>>> - mutex_init(&client->lock); >>>> + __mutex_init(&client->lock, "host1x client lock", key); >>> >>> Should we maybe attempt to make this unique? Could we use something like >>> dev_name(client->dev) for this? >> >> I'm curious who the lockdep warning could be triggered at all, I don't >> recall ever seeing it. Mikko, could you please clarify how to reproduce >> the warning? >> > > This is pretty difficult to read but I guess it's some interaction > related to the delayed initialization of host1x clients? In any case, I > consistently get it at boot (though it may be triggered by vic probe > instead of nvdec). > > I'll fix the kbuild robot warnings and see if I can add a > client-specific lock name for v6. Lockdep doesn't seem to be liking dev_name() for the name, and I think allocating a string for this purpose seems a bit overkill, so I'll keep the lock name as is if there are no objections. Mikko > > Mikko > > [ 38.128257] WARNING: possible recursive locking detected > [ 38.133567] 5.11.0-rc2-next-20210108+ #102 Tainted: G S > [ 38.140089] -------------------------------------------- > [ 38.145395] systemd-udevd/239 is trying to acquire lock: > [ 38.150703] ffff0000997aa218 (&client->lock){+.+.}-{3:3}, at: > host1x_client_resume+0x30/0x100 [host1x] > [ 38.160142] > [ 38.160142] but task is already holding lock: > [ 38.165968] ffff000080c3b148 (&client->lock){+.+.}-{3:3}, at: > host1x_client_resume+0x30/0x100 [host1x] > [ 38.175398] > [ 38.175398] other info that might help us debug this: > [ 38.181918] Possible unsafe locking scenario: > [ 38.181918] > [ 38.187830] CPU0 > [ 38.190275] ---- > [ 38.192719] lock(&client->lock); > [ 38.196129] lock(&client->lock); > [ 38.199537] > [ 38.199537] *** DEADLOCK *** > [ 38.199537] > [ 38.205449] May be due to missing lock nesting notation > [ 38.205449] > [ 38.212228] 6 locks held by systemd-udevd/239: > [ 38.216669] #0: ffff00009261c188 (&dev->mutex){....}-{3:3}, at: > device_driver_attach+0x60/0x130 > [ 38.225487] #1: ffff800009a17168 (devices_lock){+.+.}-{3:3}, at: > host1x_client_register+0x7c/0x220 [host1x] > [ 38.235441] #2: ffff000083f94bb8 (&host->devices_lock){+.+.}-{3:3}, > at: host1x_client_register+0xac/0x220 [host1x] > [ 38.245996] #3: ffff0000a2267190 (&dev->mutex){....}-{3:3}, at: > __device_attach+0x8c/0x230 > [ 38.254372] #4: ffff000092c880f0 (&wgrp->lock){+.+.}-{3:3}, at: > tegra_display_hub_prepare+0xd8/0x170 [tegra_drm] > [ 38.264788] #5: ffff000080c3b148 (&client->lock){+.+.}-{3:3}, at: > host1x_client_resume+0x30/0x100 [host1x] > [ 38.274658] > [ 38.274658] stack backtrace: > [ 38.279012] CPU: 0 PID: 239 Comm: systemd-udevd Tainted: G S > 5.11.0-rc2-next-20210108+ #102 > [ 38.288660] Hardware name: NVIDIA Jetson TX2 Developer Kit (DT) > [ 38.294577] Call trace: > [ 38.297022] dump_backtrace+0x0/0x2c0 > [ 38.300695] show_stack+0x18/0x6c > [ 38.304013] dump_stack+0x120/0x19c > [ 38.307507] __lock_acquire+0x171c/0x2c34 > [ 38.311521] lock_acquire.part.0+0x230/0x490 > [ 38.315793] lock_acquire+0x70/0x90 > [ 38.319285] __mutex_lock+0x11c/0x6d0 > [ 38.322952] mutex_lock_nested+0x58/0x90 > [ 38.326877] host1x_client_resume+0x30/0x100 [host1x] > [ 38.332047] host1x_client_resume+0x44/0x100 [host1x] > [ 38.337200] tegra_display_hub_prepare+0xf8/0x170 [tegra_drm] > [ 38.343084] host1x_drm_probe+0x1fc/0x4f0 [tegra_drm] > [ 38.348256] host1x_device_probe+0x3c/0x50 [host1x] > [ 38.353240] really_probe+0x148/0x6f0 > [ 38.356906] driver_probe_device+0x78/0xe4 > [ 38.361005] __device_attach_driver+0x10c/0x170 > [ 38.365536] bus_for_each_drv+0xf0/0x160 > [ 38.369461] __device_attach+0x168/0x230 > [ 38.373385] device_initial_probe+0x14/0x20 > [ 38.377571] bus_probe_device+0xec/0x100 > [ 38.381494] device_add+0x580/0xbcc > [ 38.384985] host1x_subdev_register+0x178/0x1cc [host1x] > [ 38.390397] host1x_client_register+0x138/0x220 [host1x] > [ 38.395808] nvdec_probe+0x240/0x3ec [tegra_drm] > [ 38.400549] platform_probe+0x8c/0x110 > [ 38.404302] really_probe+0x148/0x6f0 > [ 38.407966] driver_probe_device+0x78/0xe4 > [ 38.412065] device_driver_attach+0x120/0x130 > [ 38.416423] __driver_attach+0xb4/0x190 > [ 38.420261] bus_for_each_dev+0xe8/0x160 > [ 38.424185] driver_attach+0x34/0x44 > [ 38.427761] bus_add_driver+0x1a4/0x2b0 > [ 38.431598] driver_register+0xe0/0x210 > [ 38.435437] __platform_register_drivers+0x6c/0x104 > [ 38.440318] host1x_drm_init+0x54/0x1000 [tegra_drm] > [ 38.445405] do_one_initcall+0xec/0x5e0 > [ 38.449244] do_init_module+0xe0/0x384 > [ 38.453000] load_module+0x32d8/0x3c60 _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-03-26 14:55 UTC|newest] Thread overview: 195+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-11 12:59 [PATCH v5 00/21] Host1x/TegraDRM UAPI Mikko Perttunen 2021-01-11 12:59 ` Mikko Perttunen 2021-01-11 12:59 ` [PATCH v5 01/21] gpu: host1x: Use different lock classes for each client Mikko Perttunen 2021-01-11 12:59 ` Mikko Perttunen 2021-03-22 14:46 ` Thierry Reding 2021-03-22 14:46 ` Thierry Reding 2021-03-22 14:48 ` Dmitry Osipenko 2021-03-22 14:48 ` Dmitry Osipenko 2021-03-22 15:19 ` Mikko Perttunen 2021-03-22 15:19 ` Mikko Perttunen 2021-03-22 16:01 ` Dmitry Osipenko 2021-03-22 16:01 ` Dmitry Osipenko 2021-03-23 10:20 ` Thierry Reding 2021-03-23 10:20 ` Thierry Reding 2021-03-23 13:25 ` Dmitry Osipenko 2021-03-23 13:25 ` Dmitry Osipenko 2021-03-26 14:54 ` Mikko Perttunen [this message] 2021-03-26 14:54 ` Mikko Perttunen 2021-03-26 18:31 ` Dmitry Osipenko 2021-03-26 18:31 ` Dmitry Osipenko 2021-03-26 19:10 ` Mikko Perttunen 2021-03-26 19:10 ` Mikko Perttunen 2021-03-26 22:47 ` Dmitry Osipenko 2021-03-26 22:47 ` Dmitry Osipenko 2021-01-11 13:00 ` [PATCH v5 02/21] gpu: host1x: Allow syncpoints without associated client Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-03-23 10:10 ` Thierry Reding 2021-03-23 10:10 ` Thierry Reding 2021-03-23 10:32 ` Mikko Perttunen 2021-03-23 10:32 ` Mikko Perttunen 2021-01-11 13:00 ` [PATCH v5 03/21] gpu: host1x: Show number of pending waiters in debugfs Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-03-23 10:16 ` Thierry Reding 2021-03-23 10:16 ` Thierry Reding 2021-03-26 14:34 ` Mikko Perttunen 2021-03-26 14:34 ` Mikko Perttunen 2021-04-01 21:19 ` Michał Mirosław 2021-04-01 21:19 ` Michał Mirosław 2021-04-02 16:02 ` Dmitry Osipenko 2021-04-02 16:02 ` Dmitry Osipenko 2021-04-08 4:13 ` Michał Mirosław 2021-04-08 4:13 ` Michał Mirosław 2021-04-08 4:25 ` Michał Mirosław 2021-04-08 4:25 ` Michał Mirosław 2021-04-08 11:58 ` Mikko Perttunen 2021-04-08 11:58 ` Mikko Perttunen 2021-01-11 13:00 ` [PATCH v5 04/21] gpu: host1x: Remove cancelled waiters immediately Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-01-12 22:07 ` Dmitry Osipenko 2021-01-12 22:07 ` Dmitry Osipenko 2021-01-12 22:20 ` Mikko Perttunen 2021-01-12 22:20 ` Mikko Perttunen 2021-01-13 16:29 ` Dmitry Osipenko 2021-01-13 16:29 ` Dmitry Osipenko 2021-01-13 18:16 ` Mikko Perttunen 2021-01-13 18:16 ` Mikko Perttunen 2021-03-23 10:23 ` Thierry Reding 2021-03-23 10:23 ` Thierry Reding 2021-01-11 13:00 ` [PATCH v5 05/21] gpu: host1x: Use HW-equivalent syncpoint expiration check Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-03-23 10:26 ` Thierry Reding 2021-03-23 10:26 ` Thierry Reding 2021-01-11 13:00 ` [PATCH v5 06/21] gpu: host1x: Cleanup and refcounting for syncpoints Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-03-23 10:36 ` Thierry Reding 2021-03-23 10:36 ` Thierry Reding 2021-03-23 10:44 ` Mikko Perttunen 2021-03-23 10:44 ` Mikko Perttunen 2021-03-23 11:21 ` Thierry Reding 2021-03-23 11:21 ` Thierry Reding 2021-01-11 13:00 ` [PATCH v5 07/21] gpu: host1x: Introduce UAPI header Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-03-23 10:52 ` Thierry Reding 2021-03-23 10:52 ` Thierry Reding 2021-03-23 11:12 ` Mikko Perttunen 2021-03-23 11:12 ` Mikko Perttunen 2021-03-23 11:43 ` Thierry Reding 2021-03-23 11:43 ` Thierry Reding 2021-01-11 13:00 ` [PATCH v5 08/21] gpu: host1x: Implement /dev/host1x device node Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-03-23 11:02 ` Thierry Reding 2021-03-23 11:02 ` Thierry Reding 2021-03-23 11:15 ` Mikko Perttunen 2021-03-23 11:15 ` Mikko Perttunen 2021-01-11 13:00 ` [PATCH v5 09/21] gpu: host1x: DMA fences and userspace fence creation Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-03-23 11:15 ` Thierry Reding 2021-03-23 11:15 ` Thierry Reding 2021-01-11 13:00 ` [PATCH v5 10/21] gpu: host1x: Add no-recovery mode Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-01-11 13:00 ` [PATCH v5 11/21] gpu: host1x: Add job release callback Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-03-23 11:55 ` Thierry Reding 2021-03-23 11:55 ` Thierry Reding 2021-01-11 13:00 ` [PATCH v5 12/21] gpu: host1x: Add support for syncpoint waits in CDMA pushbuffer Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-01-11 13:00 ` [PATCH v5 13/21] gpu: host1x: Reset max value when freeing a syncpoint Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-01-11 13:00 ` [PATCH v5 14/21] gpu: host1x: Reserve VBLANK syncpoints at initialization Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-01-11 13:00 ` [PATCH v5 15/21] drm/tegra: Add new UAPI to header Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-01-13 18:14 ` Dmitry Osipenko 2021-01-13 18:14 ` Dmitry Osipenko 2021-01-13 18:56 ` Mikko Perttunen 2021-01-13 18:56 ` Mikko Perttunen 2021-01-14 8:36 ` Dmitry Osipenko 2021-01-14 8:36 ` Dmitry Osipenko 2021-01-14 10:34 ` Mikko Perttunen 2021-01-14 10:34 ` Mikko Perttunen 2021-03-23 12:30 ` Thierry Reding 2021-03-23 12:30 ` Thierry Reding 2021-03-23 14:00 ` Dmitry Osipenko 2021-03-23 14:00 ` Dmitry Osipenko 2021-03-23 16:44 ` Thierry Reding 2021-03-23 16:44 ` Thierry Reding 2021-03-23 17:32 ` Dmitry Osipenko 2021-03-23 17:32 ` Dmitry Osipenko 2021-03-23 17:57 ` Thierry Reding 2021-03-23 17:57 ` Thierry Reding 2021-01-11 13:00 ` [PATCH v5 16/21] drm/tegra: Boot VIC during runtime PM resume Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-01-11 13:00 ` [PATCH v5 17/21] drm/tegra: Set resv fields when importing/exporting GEMs Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-01-11 13:00 ` [PATCH v5 18/21] drm/tegra: Allocate per-engine channel in core code Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-03-23 12:35 ` Thierry Reding 2021-03-23 12:35 ` Thierry Reding 2021-03-23 13:15 ` Mikko Perttunen 2021-03-23 13:15 ` Mikko Perttunen 2021-01-11 13:00 ` [PATCH v5 19/21] drm/tegra: Implement new UAPI Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-01-11 17:37 ` kernel test robot 2021-01-11 17:37 ` kernel test robot 2021-01-11 17:37 ` kernel test robot 2021-01-12 22:27 ` Dmitry Osipenko 2021-01-12 22:27 ` Dmitry Osipenko 2021-03-23 13:25 ` Thierry Reding 2021-03-23 13:25 ` Thierry Reding 2021-03-23 14:43 ` Mikko Perttunen 2021-03-23 14:43 ` Mikko Perttunen 2021-03-23 15:00 ` Dmitry Osipenko 2021-03-23 15:00 ` Dmitry Osipenko 2021-03-23 16:59 ` Thierry Reding 2021-03-23 16:59 ` Thierry Reding 2021-01-11 13:00 ` [PATCH v5 20/21] drm/tegra: Implement job submission part of " Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-03-23 13:38 ` Thierry Reding 2021-03-23 13:38 ` Thierry Reding 2021-03-23 14:16 ` Mikko Perttunen 2021-03-23 14:16 ` Mikko Perttunen 2021-03-23 17:04 ` Thierry Reding 2021-03-23 17:04 ` Thierry Reding 2021-01-11 13:00 ` [PATCH v5 21/21] drm/tegra: Add job firewall Mikko Perttunen 2021-01-11 13:00 ` Mikko Perttunen 2021-01-19 22:29 ` [PATCH v5 00/21] Host1x/TegraDRM UAPI Dmitry Osipenko 2021-01-19 22:29 ` Dmitry Osipenko 2021-01-26 2:45 ` Mikko Perttunen 2021-01-26 2:45 ` Mikko Perttunen 2021-01-27 21:20 ` [PATCH v5 00/21] Host1x sync point UAPI should not be used for tracking DRM jobs Dmitry Osipenko 2021-01-27 21:20 ` Dmitry Osipenko 2021-01-28 11:08 ` Mikko Perttunen 2021-01-28 11:08 ` Mikko Perttunen 2021-01-28 16:58 ` Thierry Reding 2021-01-28 16:58 ` Thierry Reding 2021-01-29 17:30 ` Dmitry Osipenko 2021-01-29 17:30 ` Dmitry Osipenko 2021-02-03 11:18 ` Mikko Perttunen 2021-02-03 11:18 ` Mikko Perttunen 2021-02-27 11:19 ` Dmitry Osipenko 2021-02-27 11:19 ` Dmitry Osipenko 2021-03-01 8:19 ` Mikko Perttunen 2021-03-01 8:19 ` Mikko Perttunen 2021-03-23 18:21 ` Thierry Reding 2021-03-23 18:21 ` Thierry Reding 2021-03-23 19:57 ` Dmitry Osipenko 2021-03-23 19:57 ` Dmitry Osipenko 2021-03-23 20:13 ` Dmitry Osipenko 2021-03-23 20:13 ` Dmitry Osipenko 2021-01-27 21:26 ` [PATCH v5 00/21] Host1x/TegraDRM UAPI Dmitry Osipenko 2021-01-27 21:26 ` Dmitry Osipenko 2021-01-27 21:57 ` Mikko Perttunen 2021-01-27 21:57 ` Mikko Perttunen 2021-01-27 22:06 ` Dmitry Osipenko 2021-01-27 22:06 ` Dmitry Osipenko 2021-01-28 11:46 ` Mikko Perttunen 2021-01-28 11:46 ` Mikko Perttunen 2021-01-27 21:35 ` [PATCH v5 00/21] sync_file API is not very suitable for DRM Dmitry Osipenko 2021-01-27 21:35 ` Dmitry Osipenko 2021-01-27 21:53 ` Mikko Perttunen 2021-01-27 21:53 ` Mikko Perttunen 2021-01-27 22:26 ` Dmitry Osipenko 2021-01-27 22:26 ` Dmitry Osipenko 2021-01-27 21:52 ` [PATCH v5 00/21] support option where all commands are collected into a single,dedicated cmdstream Dmitry Osipenko 2021-01-27 21:52 ` Dmitry Osipenko
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=0fb1b458-66bb-c9d8-04c7-174165b39811@kapsi.fi \ --to=cyndis@kapsi.fi \ --cc=airlied@linux.ie \ --cc=bhuntsman@nvidia.com \ --cc=daniel@ffwll.ch \ --cc=digetx@gmail.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=jonathanh@nvidia.com \ --cc=linux-tegra@vger.kernel.org \ --cc=mperttunen@nvidia.com \ --cc=talho@nvidia.com \ --cc=thierry.reding@gmail.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: 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.