From: Zefan Li <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>, <keescook@chromium.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Subject: [PATCH 2/3] sched: add a macro to define bitops for task atomic flags
Date: Mon, 22 Sep 2014 11:51:48 +0800 [thread overview]
Message-ID: <541F9CD4.5040407@huawei.com> (raw)
In-Reply-To: <541F9C96.10705@huawei.com>
This will simplify code when we add new flags.
Signed-off-by: Zefan Li <lizefan@huawei.com>
---
include/linux/sched.h | 20 +++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/include/linux/sched.h b/include/linux/sched.h
index 4557765..04a2ae2 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1959,15 +1959,17 @@ static inline void memalloc_noio_restore(unsigned int flags)
/* Per-process atomic flags. */
#define PFA_NO_NEW_PRIVS 0 /* May not gain new privileges. */
-static inline bool task_no_new_privs(struct task_struct *p)
-{
- return test_bit(PFA_NO_NEW_PRIVS, &p->atomic_flags);
-}
-
-static inline void task_set_no_new_privs(struct task_struct *p)
-{
- set_bit(PFA_NO_NEW_PRIVS, &p->atomic_flags);
-}
+#define TASK_PFA_BITOPS(name, func) \
+static inline bool task_##func(struct task_struct *p) \
+{ return test_bit(PFA_##name, &p->atomic_flags); } \
+ \
+static inline void task_set_##func(struct task_struct *p) \
+{ set_bit(PFA_##name, &p->atomic_flags); } \
+ \
+static inline void task_clear_##func(struct task_struct *p) \
+{ clear_bit(PFA_##name, &p->atomic_flags); }
+
+TASK_PFA_BITOPS(NO_NEW_PRIVS, no_new_privs)
/*
* task->jobctl flags
--
1.8.0.2
next prev parent reply other threads:[~2014-09-22 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 3:50 [PATCH 1/3] sched: fix confusing PFA_NO_NEW_PRIVS constant Zefan Li
2014-09-22 3:51 ` Zefan Li [this message]
2014-09-22 11:45 ` [PATCH 2/3] sched: add a macro to define bitops for task atomic flags Peter Zijlstra
2014-09-22 3:52 ` [PATCH 3/3] cpuset: PF_SPREAD_PAGE and PF_SPREAD_SLAB should be " Zefan Li
2014-09-22 4:02 ` [PATCH 1/3] sched: fix confusing PFA_NO_NEW_PRIVS constant Tejun Heo
2014-09-22 4:44 ` Zefan Li
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=541F9CD4.5040407@huawei.com \
--to=lizefan@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).