public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Mike Travis <travis@sgi.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, 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 12:12:33 -0700	[thread overview]
Message-ID: <488F6BA1.4030708@goop.org> (raw)
In-Reply-To: <488F6563.4000907@sgi.com>

Mike Travis wrote:
> Should there be a "generic" X86_ENTERPRISE_ARCH which turns on various
> capabilities?  Our licenses and support agreements with SuSE and RH are
> for their "Enterprise Editions" though the customer is free to run
> whatever (unsupported from us).  Asking distros to enable that option
> should be a no-brainer.  And it could be defaulted ON with the comment
> to turn it off if you have a small desktop system.  This way they won't
> forget... ;-)  [Actually, this could turn on MAXSMP as well.]
>   

I don't have a strong opinion, but I suspect that distros actually pay 
attention to each option being set, since they end up having to support 
them all anyway.  As such, they'd generally prefer to explicitly turn 
each thing on or off themselves, and big-switch config options aren't 
all that useful.

But you would have to talk to a distro person to get confirmation ;)

    J

      reply	other threads:[~2008-07-29 19:12 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
2008-07-29 18:25         ` Jeremy Fitzhardinge
2008-07-29 18:45           ` Mike Travis
2008-07-29 19:12             ` Jeremy Fitzhardinge [this message]

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=488F6BA1.4030708@goop.org \
    --to=jeremy@goop.org \
    --cc=cpw@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=steiner@sgi.com \
    --cc=travis@sgi.com \
    --cc=yhlu.kernel@gmail.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