From: Cliff Wickman <cpw@sgi.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 1 of 6] x86, UV: smp_processor_id in a preemptable region
Date: Wed, 15 Jun 2011 13:58:01 -0500 [thread overview]
Message-ID: <20110615185801.GA2461@sgi.com> (raw)
In-Reply-To: <4DF8EA26.2000301@zytor.com>
On Wed, Jun 15, 2011 at 10:21:42AM -0700, H. Peter Anvin wrote:
> On 06/15/2011 09:40 AM, Cliff Wickman wrote:
> >
> > So would you say I should really widen the scope of the non-preemptible
> > region to include everything done with the results of that call to
> > smp_processor_id()?
> > Which in this case is the call to parse_tunables_write().
> > Like this:
> >
> > preempt_disable();
> > bcp = &per_cpu(bau_control, smp_processor_id());
> >
> > ret = parse_tunables_write(bcp, instr, count);
> > preempt_enable_no_resched();
> >
>
> Funny enough, this is such a common pattern that we have helpers for it.
> We call this get_cpu() ... put_cpu().
>
> -hpa
OK thanks. I'll use them.
I'll fix that patch (1 of 8) and refresh/resend the whole series after a
little time to allow for more reviews of the others.
-Cliff
--
Cliff Wickman
SGI
cpw@sgi.com
(651) 683-3824
prev parent reply other threads:[~2011-06-15 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 23:06 [PATCH 1 of 6] x86, UV: smp_processor_id in a preemptable region Cliff Wickman
2011-06-15 6:05 ` Rakib Mullick
2011-06-15 13:52 ` Cliff Wickman
2011-06-15 15:54 ` Ingo Molnar
2011-06-15 16:07 ` Cliff Wickman
2011-06-15 16:15 ` Ingo Molnar
2011-06-15 16:40 ` Cliff Wickman
2011-06-15 17:21 ` H. Peter Anvin
2011-06-15 18:58 ` Cliff Wickman [this message]
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=20110615185801.GA2461@sgi.com \
--to=cpw@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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