From: Borislav Petkov <petkovbb@googlemail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Borislav Petkov <borislav.petkov@amd.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [x86, msr]: execute on the correct CPU subset
Date: Wed, 29 Jul 2009 20:02:44 +0200 [thread overview]
Message-ID: <20090729180244.GA28534@liondog.tnic> (raw)
In-Reply-To: <4A708745.5040203@zytor.com>
On Wed, Jul 29, 2009 at 10:30:45AM -0700, H. Peter Anvin wrote:
> On 07/29/2009 09:49 AM, Borislav Petkov wrote:
> > On Mon, Jul 27, 2009 at 01:46:26PM -0700, H. Peter Anvin wrote:
> >> Any reason not to use get_cpu() ... put_cpu() instead?
> >
> > In case you haven't applied the one from yesterday yet, here's a better
> > one which uses struct cpumask * instead of cpumask_t.
> >
>
> Mangled patch (quoted-printable).
Sorry about that, will resend tomorrow.
> Furthermore, are there any users for this interface at this time?
Yep, drivers/edac/amd64_edac.c.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2009-07-29 18:09 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
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 [this message]
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=20090729180244.GA28534@liondog.tnic \
--to=petkovbb@googlemail.com \
--cc=borislav.petkov@amd.com \
--cc=hpa@zytor.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 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®