From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: "Cliff Wickman" <cpw@sgi.com>,
"Nick Piggin" <nickpiggin@yahoo.com.au>,
steiner@sgi.com, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: Comments on UV tlb flushing
Date: Tue, 29 Jul 2008 11:13:16 -0700 [thread overview]
Message-ID: <86802c440807291113u59ba996dg340c8feba1039f3a@mail.gmail.com> (raw)
In-Reply-To: <488F2C9B.9070306@goop.org>
On Tue, Jul 29, 2008 at 7:43 AM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Cliff Wickman wrote:
>>
>> I think that the Linux distributions are not going to build a special
>> UV kernel, are they? So every distro would have to be prompted to turn on
>> CONFIG_X86_UV, or else their kernel is not going to boot on UV.
>>
>
> Distros will generally turn on everything. You could have it on by default
> if the kernel is built for CONFIG_X86_GENERICARCH which enables support for
> other big numa configurations. I think distros generally build with that
> enabled anyway.
config X86_GENERICARCH
bool "Generic architecture"
depends on X86_32
help
This option compiles in the NUMAQ, Summit, bigsmp, ES7000, default
subarchitectures. It is intended for a generic binary kernel.
if you select them all, kernel will probe it one by one. and will
fallback to default.
YH
next prev parent reply other threads:[~2008-07-29 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 0:28 Comments on UV tlb flushing Jeremy Fitzhardinge
2008-07-29 4:12 ` Nick Piggin
2008-07-29 6:26 ` Jeremy Fitzhardinge
2008-07-29 13:32 ` Cliff Wickman
2008-07-29 14:43 ` Jeremy Fitzhardinge
2008-07-29 17:34 ` Cliff Wickman
2008-07-29 17:46 ` Jeremy Fitzhardinge
2008-07-29 20:04 ` Cliff Wickman
2008-07-29 18:13 ` Yinghai Lu [this message]
2008-07-29 18:25 ` Jeremy Fitzhardinge
2008-07-29 18:45 ` Mike Travis
2008-07-29 19:12 ` Jeremy Fitzhardinge
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=86802c440807291113u59ba996dg340c8feba1039f3a@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=cpw@sgi.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=steiner@sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).