From: Matthew Brost <matthew.brost@intel.com>
To: Tejun Heo <tj@kernel.org>
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: [RFC PATCH 1/3] workqueue: Add interface for user-defined workqueue lockdep map
Date: Tue, 30 Jul 2024 22:56:52 +0000 [thread overview]
Message-ID: <ZqlvtJs6lmEwqgzv@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <ZqlvkdIoZAkVrvvx@slm.duckdns.org>
On Tue, Jul 30, 2024 at 12:56:17PM -1000, Tejun Heo wrote:
> On Tue, Jul 30, 2024 at 10:53:38PM +0000, Matthew Brost wrote:
> > I didn't want to change the export alloc_workqueue() arguments so I went
> > with this approach. Are you suggesting export a new function
> > alloc_workqueue_lockdep_map() which will share an internal
> > implementation with the existing alloc_workqueue() but passes in a
> > lockdep map? That could work.
>
> Yeah, add a new exported function which takes lockdep_map and make
> alloc_workqueue() to call that with the embedded map. No need to make the
> latter inline either.
>
Sure, let me do that.
Matt
> Thanks.
>
> --
> tejun
next prev parent reply other threads:[~2024-07-30 22:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 22:17 [RFC PATCH 0/3] Use user-defined workqueue lockdep map for drm sched Matthew Brost
2024-07-30 22:17 ` [RFC PATCH 1/3] workqueue: Add interface for user-defined workqueue lockdep map Matthew Brost
2024-07-30 22:34 ` Tejun Heo
2024-07-30 22:53 ` Matthew Brost
2024-07-30 22:56 ` Tejun Heo
2024-07-30 22:56 ` Matthew Brost [this message]
2024-07-30 22:17 ` [RFC PATCH 2/3] drm/sched: Use drm sched lockdep map for submit_wq Matthew Brost
2024-07-30 22:17 ` [RFC PATCH 3/3] drm/xe: Drop GuC submit_wq pool Matthew Brost
2024-07-30 22:22 ` ✓ CI.Patch_applied: success for Use user-defined workqueue lockdep map for drm sched Patchwork
2024-07-30 22:22 ` ✓ CI.checkpatch: " Patchwork
2024-07-30 22:23 ` ✓ CI.KUnit: " Patchwork
2024-07-30 22:35 ` ✓ CI.Build: " Patchwork
2024-07-30 22:37 ` ✓ CI.Hooks: " Patchwork
2024-07-30 22:39 ` ✗ CI.checksparse: warning " Patchwork
2024-07-30 22:58 ` ✓ CI.BAT: success " Patchwork
2024-07-31 0:11 ` ✗ CI.FULL: failure " 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=ZqlvtJs6lmEwqgzv@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--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=tj@kernel.org \
/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