From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jack Steiner <steiner@sgi.com>, Andi Kleen <andi@firstfloor.org>,
tglx@linutronix.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 8/8] x86_64: Support for new UV apic
Date: Sun, 30 Mar 2008 13:23:12 -0700 [thread overview]
Message-ID: <86802c440803301323q5c4bd4f4k1f9bdc1d6b1a0a7b@mail.gmail.com> (raw)
In-Reply-To: <20080326073823.GD3442@elte.hu>
On Wed, Mar 26, 2008 at 12:38 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Jack Steiner <steiner@sgi.com> wrote:
>
> > > > - obj-y += genapic_64.o genapic_flat_64.o
> > > > + obj-y += genapic_64.o genapic_flat_64.o genx2apic_uv_x.o
> > >
> > > Definitely should be a CONFIG
> >
> > Not sure that I understand why. The overhead of UV is minimal & we
> > want UV enabled in all distro kernels. OTOH, small embedded systems
> > probably want to eliminate every last bit of unneeded code.
> >
> > Might make sense to have a config option. Thoughts????
>
> i wouldnt mind having UV enabled by default (it can be a config option
> but default-enabled on generic kernels so all distros will pick this hw
> support up), but we definitely need the genapic unification before we
> can add more features.
config option would be reasonable.
for x86_64
subarch already have X86_PC, X86_VSMP.
we have X86_UVSMP
YH
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-03-30 20:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 18:21 Jack Steiner
2008-03-25 10:25 ` Andi Kleen
2008-03-25 17:56 ` Jack Steiner
2008-03-25 18:06 ` Andi Kleen
2008-03-26 2:23 ` Jeremy Fitzhardinge
2008-03-26 3:22 ` Glauber Costa
2008-03-26 7:29 ` Ingo Molnar
2008-03-26 7:38 ` Ingo Molnar
2008-03-30 20:23 ` Yinghai Lu [this message]
2008-03-30 21:03 ` Jack Steiner
2008-03-30 21:18 ` Andi Kleen
2008-03-30 23:29 ` Yinghai Lu
2008-03-31 2:18 ` Jack Steiner
2008-03-31 2:20 ` Yinghai Lu
2008-03-31 12:33 ` Ingo Molnar
2008-03-31 12:52 ` Andi Kleen
2008-03-31 18:42 ` Yinghai Lu
2008-03-31 6:48 ` Andi Kleen
2008-03-25 14:30 ` Ingo Molnar
2008-03-25 16:31 ` Jack Steiner
2008-03-26 3:24 ` Glauber Costa
2008-03-30 20:41 ` Yinghai Lu
2008-03-30 21:08 ` Jack Steiner
2008-03-30 23:24 ` Yinghai Lu
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=86802c440803301323q5c4bd4f4k1f9bdc1d6b1a0a7b@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--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