From: Muchun Song <smuchun@gmail.com>
To: joel@joelfernandes.org, tglx@linutronix.de, mingo@kernel.org,
rostedt@goodmis.org, frederic@kernel.org,
paulmck@linux.vnet.ibm.com, alexander.levin@verizon.com,
peterz@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] softirq: Replace this_cpu_write with __this_cpu_write if irq is disabled
Date: Tue, 18 Jun 2019 22:33:05 +0800 [thread overview]
Message-ID: <20190618143305.2038-1-smuchun@gmail.com> (raw)
Irq is disabled before this_cpu_write(), so we can Replace this_cpu_write()
with __this_cpu_write().
Signed-off-by: Muchun Song <smuchun@gmail.com>
---
kernel/softirq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/softirq.c b/kernel/softirq.c
index 2c3382378d94..eaf3bdf7c749 100644
--- a/kernel/softirq.c
+++ b/kernel/softirq.c
@@ -650,7 +650,7 @@ static int takeover_tasklets(unsigned int cpu)
/* Find end, append list for that CPU. */
if (&per_cpu(tasklet_vec, cpu).head != per_cpu(tasklet_vec, cpu).tail) {
*__this_cpu_read(tasklet_vec.tail) = per_cpu(tasklet_vec, cpu).head;
- this_cpu_write(tasklet_vec.tail, per_cpu(tasklet_vec, cpu).tail);
+ __this_cpu_write(tasklet_vec.tail, per_cpu(tasklet_vec, cpu).tail);
per_cpu(tasklet_vec, cpu).head = NULL;
per_cpu(tasklet_vec, cpu).tail = &per_cpu(tasklet_vec, cpu).head;
}
--
2.17.1
next reply other threads:[~2019-06-18 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 14:33 Muchun Song [this message]
2019-06-23 16:19 ` [tip:irq/core] softirq: Use __this_cpu_write() in takeover_tasklets() tip-bot for Muchun Song
2019-06-24 23:04 ` [PATCH] softirq: Replace this_cpu_write with __this_cpu_write if irq is disabled Paul E. McKenney
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=20190618143305.2038-1-smuchun@gmail.com \
--to=smuchun@gmail.com \
--cc=alexander.levin@verizon.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®