From: Nick Piggin <npiggin@suse.de>
To: Mike Travis <travis@sgi.com>
Cc: Jack Steiner <steiner@sgi.com>,
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 16:04:44 +0100 [thread overview]
Message-ID: <20090106150444.GI16738@wotan.suse.de> (raw)
In-Reply-To: <49637090.8010501@sgi.com>
On Tue, Jan 06, 2009 at 06:54:08AM -0800, Mike Travis wrote:
> 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.
> >
> >
> > --- jack
>
> Nick - would you add something like this to your patch? Thanks! Mike
> ---
> Subject: x86: enable UV when MAXSMP is configured.
>
> We want UV code to be tested even for non-UV architectures. Enabling
> MAXSMP specifies "maximizing the system capabitlity" and UV is one of
> these methods. Also helps distros select the correct config options
> for their default configurations.
I don't really follow. The config option I added is very visible and
clear, isn't it? I don't think MAXSMP means that, otherwise it would
basically be allyesconfig.
I wouldn't object to have a platform types menu like the processor
types one. Or a generic architecture checkbox to select some of
these things together.
next prev parent reply other threads:[~2009-01-06 15:04 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
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 [this message]
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=20090106150444.GI16738@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 \
--cc=travis@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
Powered by JetHome