From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Masami Hiramatsu <mhiramat@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use test_and_clear_bit() instead atomic_dec_and_test() for stop_machine
Date: Wed, 23 May 2012 13:19:14 +0900 [thread overview]
Message-ID: <87mx4zr0l9.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <87aa0zty4r.fsf@devron.myhome.or.jp> (OGAWA Hirofumi's message of "Wed, 23 May 2012 11:44:04 +0900")
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
>> The down side to this is that it adds 4 more bytes on a 64bit
>> machine. (sizeof(unsigned log) == 8 and sizeof(atomic_t) == 4)
Another patch without additional 4bytes. This simply change
atomic_dec_and_test() to atomic_xchg().
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
stop_machine_first is just to see if it is first one or not. In this
usage, atomic_dec_and_test() makes value less than 0.
I think it is not desirable, because it only triggers
atomic_dec_and_test() less than 0 debug patch. (the patch tests result
of atomic_dec_and_test() is < 0)
So, this uses atomic_xchg() instead.
Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
---
arch/x86/kernel/alternative.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN arch/x86/kernel/alternative.c~stop_machine-use-atomic_xchg arch/x86/kernel/alternative.c
--- linux/arch/x86/kernel/alternative.c~stop_machine-use-atomic_xchg 2012-05-23 13:10:03.000000000 +0900
+++ linux-hirofumi/arch/x86/kernel/alternative.c 2012-05-23 13:10:03.000000000 +0900
@@ -664,7 +664,7 @@ static int __kprobes stop_machine_text_p
struct text_poke_param *p;
int i;
- if (atomic_dec_and_test(&stop_machine_first)) {
+ if (atomic_xchg(&stop_machine_first, 0)) {
for (i = 0; i < tpp->nparams; i++) {
p = &tpp->params[i];
text_poke(p->addr, p->opcode, p->len);
_
next prev parent reply other threads:[~2012-05-23 4:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87likkt7u6.fsf@devron.myhome.or.jp>
2012-05-22 18:11 ` OGAWA Hirofumi
2012-05-22 21:46 ` Steven Rostedt
2012-05-23 2:44 ` OGAWA Hirofumi
2012-05-23 4:19 ` OGAWA Hirofumi [this message]
2012-05-23 8:43 ` Steven Rostedt
2012-06-07 12:54 ` Steven Rostedt
2012-06-07 13:18 ` OGAWA Hirofumi
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=87mx4zr0l9.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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®