From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [x86, msr]: execute on the correct CPU subset
Date: Mon, 27 Jul 2009 13:46:26 -0700 [thread overview]
Message-ID: <4A6E1222.5010709@zytor.com> (raw)
In-Reply-To: <20090708111911.GC19315@aftab>
Borislav Petkov wrote:
>
> preempt_disable();
> - /*
> - * FIXME: handle the CPU we're executing on separately for now until
> - * smp_call_function_many has been fixed to not skip it.
> - */
> this_cpu = raw_smp_processor_id();
> - smp_call_function_single(this_cpu, __rdmsr_on_cpu, &rv, 1);
>
> - smp_call_function_many(mask, __rdmsr_on_cpu, &rv, 1);
> + if (cpumask_test_cpu(this_cpu, mask))
> + msr_func(&rv);
> +
> + smp_call_function_many(mask, msr_func, &rv, 1);
> preempt_enable();
> }
Any reason not to use get_cpu() ... put_cpu() instead?
-hpa
next prev parent reply other threads:[~2009-07-27 20:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 14:29 [PATCH] [x86, msr]: remove code duplication Borislav Petkov
2009-07-06 21:31 ` H. Peter Anvin
2009-07-07 10:37 ` Borislav Petkov
2009-07-07 15:56 ` H. Peter Anvin
2009-07-08 11:19 ` [PATCH] [x86, msr]: execute on the correct CPU subset (was: Re: [PATCH] [x86, msr]: remove code duplication) Borislav Petkov
2009-07-16 16:51 ` Borislav Petkov
2009-07-16 17:24 ` [PATCH] [x86, msr]: execute on the correct CPU subset H. Peter Anvin
2009-07-27 20:46 ` H. Peter Anvin [this message]
2009-07-28 10:29 ` Borislav Petkov
2009-07-29 16:49 ` Borislav Petkov
2009-07-29 17:30 ` H. Peter Anvin
2009-07-29 18:02 ` Borislav Petkov
2009-07-29 18:05 ` H. Peter Anvin
2009-07-29 18:46 ` Borislav Petkov
2009-07-29 18:50 ` H. Peter Anvin
2009-07-30 9:10 ` [PATCH] x86, msr: " Borislav Petkov
2009-07-30 9:10 ` [PATCH] x86, msr: unify rdmsr_on_cpus/wrmsr_on_cpus Borislav Petkov
2009-09-14 12:55 ` Borislav Petkov
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=4A6E1222.5010709@zytor.com \
--to=hpa@zytor.com \
--cc=borislav.petkov@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.