From: Byungchul Park <byungchul.park@lge.com>
To: tj@kernel.org, johannes.berg@intel.com, peterz@infradead.org,
mingo@kernel.org
Cc: tglx@linutronix.de, oleg@redhat.com, david@fromorbit.com,
linux-kernel@vger.kernel.org, kernel-team@lge.com
Subject: Re: [PATCH v2 1/2] completion: Add support for initializing completion with lockdep_map
Date: Mon, 11 Sep 2017 14:44:57 +0900 [thread overview]
Message-ID: <20170911054457.GE3240@X58A-UD3R> (raw)
In-Reply-To: <1504860385-17371-1-git-send-email-byungchul.park@lge.com>
On Fri, Sep 08, 2017 at 05:46:24PM +0900, Byungchul Park wrote:
> To peter,
>
> Does it work?
>
> Chagnes from v1
> - Add a completion initialization function with a lockdep map
> - Enhance readability of the workqueue code
Do not you like it becasue it introduces another init_completion_xxx()?
Anyway, I think the redundant acquisitions in the workqueue code should
be removed. Right?
> ----->8-----
> >From e148617e20ebc9c9eefe7bb222b9bba07cb963bc Mon Sep 17 00:00:00 2001
> From: Byungchul Park <byungchul.park@lge.com>
> Date: Fri, 8 Sep 2017 17:39:48 +0900
> Subject: [PATCH v2 1/2] completion: Add support for initializing completion
> with lockdep_map
>
> Sometimes, we want to initialize completions with sparate lockdep maps
> to assign lock classes under control. For example, the workqueue code
> manages lockdep maps, as it can classify lockdep maps properly.
> Provided a function for that purpose.
>
> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> ---
> include/linux/completion.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/include/linux/completion.h b/include/linux/completion.h
> index cae5400..182d56e 100644
> --- a/include/linux/completion.h
> +++ b/include/linux/completion.h
> @@ -49,6 +49,13 @@ static inline void complete_release_commit(struct completion *x)
> lock_commit_crosslock((struct lockdep_map *)&x->map);
> }
>
> +#define init_completion_with_map(x, m) \
> +do { \
> + lockdep_init_map_crosslock((struct lockdep_map *)&(x)->map, \
> + (m)->name, (m)->key, 0); \
> + __init_completion(x); \
> +} while (0)
> +
> #define init_completion(x) \
> do { \
> static struct lock_class_key __key; \
> @@ -58,6 +65,7 @@ static inline void complete_release_commit(struct completion *x)
> __init_completion(x); \
> } while (0)
> #else
> +#define init_completion_with_map(x, m) __init_completion(x)
> #define init_completion(x) __init_completion(x)
> static inline void complete_acquire(struct completion *x) {}
> static inline void complete_release(struct completion *x) {}
> --
> 1.9.1
next prev parent reply other threads:[~2017-09-11 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 8:46 Byungchul Park
2017-09-08 8:46 ` [PATCH v2 2/2] lockdep: Remove unnecessary acquisitions wrt workqueue flush Byungchul Park
2017-09-18 8:46 ` Byungchul Park
2017-09-11 5:44 ` Byungchul Park [this message]
2017-09-26 0:53 ` [PATCH v2 1/2] completion: Add support for initializing completion with lockdep_map Byungchul Park
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=20170911054457.GE3240@X58A-UD3R \
--to=byungchul.park@lge.com \
--cc=david@fromorbit.com \
--cc=johannes.berg@intel.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®