From: Cliff Wickman <cpw@sgi.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: 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 12:34:20 -0500 [thread overview]
Message-ID: <20080729173420.GA18296@sgi.com> (raw)
In-Reply-To: <488F2C9B.9070306@goop.org>
On Tue, Jul 29, 2008 at 07:43:39AM -0700, Jeremy Fitzhardinge 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.
>
> J
I don't know much about x86 configuration options. It looks like
CONFIG_X86_GENERICARCH is fairly new, so I don't know where to look
for samples of how it will be set by RH and SuSE.
But if the tlb_uv.o code should be present in "every" distro x86 kernel
I don't see the point of having to configure it in. Why not just
configure it out for small (embedded) kernels?
-Cliff
--
Cliff Wickman
Silicon Graphics, Inc.
cpw@sgi.com
(651) 683-3824
next prev parent reply other threads:[~2008-07-29 17:34 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 [this message]
2008-07-29 17:46 ` Jeremy Fitzhardinge
2008-07-29 20:04 ` Cliff Wickman
2008-07-29 18:13 ` Yinghai Lu
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=20080729173420.GA18296@sgi.com \
--to=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 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.