From: Nick Piggin <npiggin@suse.de>
To: Jack Steiner <steiner@sgi.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, Cliff Wickman <cpw@sgi.com>,
Russ Anderson <rja@sgi.com>
Subject: Re: [patch] x86: make UV support optional
Date: Tue, 6 Jan 2009 15:48:43 +0100 [thread overview]
Message-ID: <20090106144843.GH16738@wotan.suse.de> (raw)
In-Reply-To: <20090106143330.GB18913@sgi.com>
On Tue, Jan 06, 2009 at 08:33:30AM -0600, Jack Steiner wrote:
> On Tue, Jan 06, 2009 at 07:03:48AM +0100, Nick Piggin wrote:
> > UV is fairly rare.... and much of the support is already there to cope with
> > 32-bit builds. So this makes sense I think.
> >
>
>
> Looks ok to me. One suggestion though. There is a MAXSMP config
> option. I would suggest enabling UV if MAXSMP is enabled. This
> will help ensure that UV is tested more frequently & may minimize
> regressions.
Yeah.... I don't know. OTOH it would be more logical to enable
MAXSMP iff UV is enabled (or change the MAXSMP limits for when
UV is enabled). Or you could select Intel CPUs if UV is enabled,
or disable GRU if UV is not set etc etc.
I didn't want to get too fancy with config options because arbitrary
linkages seem to just cause headaches. I figure if someone wants
to enable it, they can do so.
next prev parent reply other threads:[~2009-01-06 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 6:03 Nick Piggin
2009-01-06 6:38 ` Yinghai Lu
2009-01-06 6:44 ` Nick Piggin
2009-01-06 9:01 ` Ingo Molnar
2009-01-06 12:23 ` Nick Piggin
2009-01-06 12:31 ` Ingo Molnar
2009-01-06 14:33 ` Jack Steiner
2009-01-06 14:48 ` Nick Piggin [this message]
2009-01-06 15:05 ` Mike Travis
2009-01-06 15:30 ` Nick Piggin
2009-01-11 18:39 ` Pavel Machek
2009-01-06 14:54 ` Mike Travis
2009-01-06 15:04 ` Nick Piggin
2009-01-06 15:28 ` Ingo Molnar
2009-01-06 15:31 ` Mike Travis
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=20090106144843.GH16738@wotan.suse.de \
--to=npiggin@suse.de \
--cc=cpw@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rja@sgi.com \
--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
all inboxes | Powered by JetHome®