From: Jani Nikula <jani.nikula@linux.intel.com>
To: Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>
Cc: intel-gfx@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Radoslaw Burny <rburny@google.com>,
Byungchul Park <byungchul.park@lge.com>,
"Paul E. McKenney" <paul.mckenney@linaro.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Intel-gfx] [PATCH 05/12] drm/i915: Protect lockdep functions with #ifdef
Date: Tue, 08 Feb 2022 20:51:38 +0200 [thread overview]
Message-ID: <87y22lp4xx.fsf@intel.com> (raw)
In-Reply-To: <20220208184208.79303-6-namhyung@kernel.org>
On Tue, 08 Feb 2022, Namhyung Kim <namhyung@kernel.org> wrote:
> With upcoming lock tracepoints config, it'd define some of lockdep
> functions without enabling CONFIG_LOCKDEP actually. The existing code
> assumes those functions will be removed by the preprocessor but it's
> not the case anymore. Let's protect the code with #ifdef's explicitly.
I don't understand why you can't keep the no-op stubs for
CONFIG_LOCKDEP=n.
BR,
Jani.
>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Cc: intel-gfx@lists.freedesktop.org
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> drivers/gpu/drm/i915/intel_wakeref.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_wakeref.c b/drivers/gpu/drm/i915/intel_wakeref.c
> index dfd87d082218..6e4b8d036283 100644
> --- a/drivers/gpu/drm/i915/intel_wakeref.c
> +++ b/drivers/gpu/drm/i915/intel_wakeref.c
> @@ -106,8 +106,11 @@ void __intel_wakeref_init(struct intel_wakeref *wf,
> wf->wakeref = 0;
>
> INIT_DELAYED_WORK(&wf->work, __intel_wakeref_put_work);
> +
> +#ifdef CONFIG_LOCKDEP
> lockdep_init_map(&wf->work.work.lockdep_map,
> "wakeref.work", &key->work, 0);
> +#endif
> }
>
> int intel_wakeref_wait_for_idle(struct intel_wakeref *wf)
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-02-08 18:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 18:41 [Intel-gfx] [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1) Namhyung Kim
2022-02-08 18:42 ` [Intel-gfx] [PATCH 05/12] drm/i915: Protect lockdep functions with #ifdef Namhyung Kim
2022-02-08 18:51 ` Jani Nikula [this message]
2022-02-08 19:22 ` Namhyung Kim
2022-02-09 13:49 ` Jani Nikula
2022-02-09 16:27 ` Steven Rostedt
2022-02-09 19:28 ` Namhyung Kim
2022-02-08 19:14 ` [Intel-gfx] [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1) Namhyung Kim
2022-02-09 9:09 ` Peter Zijlstra
2022-02-09 18:19 ` Waiman Long
2022-02-09 18:29 ` Mathieu Desnoyers
2022-02-09 19:02 ` Waiman Long
2022-02-09 19:17 ` Mathieu Desnoyers
2022-02-09 19:37 ` Waiman Long
2022-02-09 19:22 ` Namhyung Kim
2022-02-09 19:28 ` Mathieu Desnoyers
2022-02-09 19:45 ` Namhyung Kim
2022-02-09 19:56 ` Mathieu Desnoyers
2022-02-09 20:17 ` Waiman Long
2022-02-10 0:27 ` Namhyung Kim
2022-02-10 2:12 ` Waiman Long
2022-02-10 9:33 ` Peter Zijlstra
2022-02-10 0:32 ` Namhyung Kim
2022-02-10 9:13 ` Peter Zijlstra
[not found] ` <20220210191404.GM4285@paulmck-ThinkPad-P17-Gen-1>
2022-02-10 19:27 ` Waiman Long
[not found] ` <20220210201058.GP4285@paulmck-ThinkPad-P17-Gen-1>
2022-02-11 5:57 ` Namhyung Kim
2022-02-11 5:55 ` Namhyung Kim
2022-02-11 10:39 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2022-02-08 19:43 [Intel-gfx] [RFC RESEND 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1.1) Namhyung Kim
2022-02-08 19:43 ` [Intel-gfx] [PATCH 05/12] drm/i915: Protect lockdep functions with #ifdef Namhyung Kim
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=87y22lp4xx.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=boqun.feng@gmail.com \
--cc=byungchul.park@lge.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paul.mckenney@linaro.org \
--cc=peterz@infradead.org \
--cc=rburny@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=will@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