From: Tejun Heo <tj@kernel.org>
To: Matthew Brost <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, jiangshanlai@gmail.com,
christian.koenig@amd.com, ltuikov89@gmail.com, daniel@ffwll.ch
Subject: Re: [PATCH v3 3/5] workqueue: Add interface for user-defined workqueue lockdep map
Date: Tue, 13 Aug 2024 09:05:12 -1000 [thread overview]
Message-ID: <ZruuaIPsEH83luku@slm.duckdns.org> (raw)
In-Reply-To: <ZrusGBG7/EkNlbsk@DUT025-TGLU.fm.intel.com>
On Tue, Aug 13, 2024 at 06:55:20PM +0000, Matthew Brost wrote:
> On Tue, Aug 13, 2024 at 08:52:26AM -1000, Tejun Heo wrote:
> > On Fri, Aug 09, 2024 at 03:28:25PM -0700, Matthew Brost wrote:
> > > Add an interface for a user-defined workqueue lockdep map, which is
> > > helpful when multiple workqueues are created for the same purpose. This
> > > also helps avoid leaking lockdep maps on each workqueue creation.
> > >
> > > v2:
> > > - Add alloc_workqueue_lockdep_map (Tejun)
> > > v3:
> > > - Drop __WQ_USER_OWNED_LOCKDEP (Tejun)
> > > - static inline alloc_ordered_workqueue_lockdep_map (Tejun)
> > >
> > > Cc: Tejun Heo <tj@kernel.org>
> > > Cc: Lai Jiangshan <jiangshanlai@gmail.com>
> > > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> >
> > 1-3 look fine to me. Would applying them to wq/for-6.12 and pulling them
> > from the dri tree work?
> >
>
> Yes, I wanted to get this into 6.12 as I believe we are removing
> forceprobe for our driver and it would be good to have this in for that.
>
> Any idea what this is about though [1]?
It looks like misattribution to me. I'll apply 1-3 to wq/for-6.12.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-08-13 19:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 22:28 [PATCH v3 0/5] Use user-defined workqueue lockdep map for drm sched Matthew Brost
2024-08-09 22:28 ` [PATCH v3 1/5] workqueue: Split alloc_workqueue into internal function and lockdep init Matthew Brost
2024-08-13 6:13 ` kernel test robot
2024-08-09 22:28 ` [PATCH v3 2/5] workqueue: Change workqueue lockdep map to pointer Matthew Brost
2024-08-09 22:28 ` [PATCH v3 3/5] workqueue: Add interface for user-defined workqueue lockdep map Matthew Brost
2024-08-12 5:03 ` Ghimiray, Himal Prasad
2024-08-13 18:52 ` Tejun Heo
2024-08-13 18:55 ` Matthew Brost
2024-08-13 19:05 ` Tejun Heo [this message]
2024-08-13 19:06 ` Tejun Heo
2024-08-09 22:28 ` [PATCH v3 4/5] drm/sched: Use drm sched lockdep map for submit_wq Matthew Brost
2024-08-12 5:35 ` Ghimiray, Himal Prasad
2024-08-13 19:16 ` Matthew Brost
2024-08-19 8:11 ` Ghimiray, Himal Prasad
2024-08-09 22:28 ` [PATCH v3 5/5] drm/xe: Drop GuC submit_wq pool Matthew Brost
2024-08-09 23:07 ` ✓ CI.Patch_applied: success for Use user-defined workqueue lockdep map for drm sched (rev3) Patchwork
2024-08-09 23:08 ` ✓ CI.checkpatch: " Patchwork
2024-08-09 23:09 ` ✓ CI.KUnit: " Patchwork
2024-08-09 23:20 ` ✓ CI.Build: " Patchwork
2024-08-09 23:23 ` ✓ CI.Hooks: " Patchwork
2024-08-09 23:24 ` ✗ CI.checksparse: warning " Patchwork
2024-08-09 23:55 ` ✗ CI.BAT: failure " Patchwork
2024-08-10 2:53 ` ✗ CI.FULL: " Patchwork
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=ZruuaIPsEH83luku@slm.duckdns.org \
--to=tj@kernel.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltuikov89@gmail.com \
--cc=matthew.brost@intel.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 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.