From: Ingo Molnar <mingo@elte.hu>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: clean up setup_clear/force_cpu_cap handling
Date: Sun, 28 Dec 2008 10:46:05 +0100 [thread overview]
Message-ID: <20081228094605.GE9022@elte.hu> (raw)
In-Reply-To: <200812282008.58544.rusty@rustcorp.com.au>
* Rusty Russell <rusty@rustcorp.com.au> wrote:
> On Saturday 27 December 2008 20:52:34 Ingo Molnar wrote:
> >
> > * Yinghai Lu <yinghai@kernel.org> wrote:
> >
> > > Impact: fix and cleanup
> > >
> > > setup_force_cpu_cap() only have one user xen
> > > but it should not reuse cleared_cpu_cpus. it will have problem
> > > for smp.
> > >
> > > need to have cpu_cpus_set array too.
> > > also need to setup handling before all cpus cap AND
> > >
> > > Signed-off-by: Yinghai Lu <yinghai.lu@kernel.org>
> > >
> > > ---
> > > arch/x86/include/asm/cpufeature.h | 4 ++--
> > > arch/x86/include/asm/processor.h | 3 ++-
> > > arch/x86/kernel/cpu/common.c | 17 ++++++++++++-----
> > > 3 files changed, 16 insertions(+), 8 deletions(-)
> >
> > Rusty, you'll carry this patch in your linux-2.6-boot-params.git tree,
> > right? Merging this in the x86 tree would just needlessly complicate your
> > logistics, right?
>
> Yep, if you're happy to ack, I'm happy to carry.
yeah. And if it breaks, that's your fault ;-)
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
prev parent reply other threads:[~2008-12-28 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 7:32 [PATCH] x86: clean up setup_clear/force_cpu_cap handling Yinghai Lu
2008-12-27 10:22 ` Ingo Molnar
2008-12-27 20:49 ` Yinghai Lu
2008-12-28 9:38 ` Rusty Russell
2008-12-28 9:46 ` Ingo Molnar [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=20081228094605.GE9022@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=yinghai@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.