mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: "Keith Mannthey" <kmannth@gmail.com>
Cc: "Randy Dunlap" <rdunlap@xenotime.net>,
	"Andrew Morton" <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] i386: require ACPI for NUMA with generic architecture
Date: Fri, 7 Jul 2006 06:21:16 -0400	[thread overview]
Message-ID: <200607070623_MC3-1-C45A-2428@compuserve.com> (raw)

In-Reply-To: <a762e240607061143s6470ad5y310986cba4f0b0bc@mail.gmail.com>

On Thu, 6 Jul 2006 11:43:37 -0700, Keith Mannthey wrote:

> On 7/6/06, Chuck Ebbert <76306.1226@compuserve.com> wrote:
> > X86 Generic Architecture (X86_GENERICARCH) includes support for
> > Summit architecture.  Enabling X86_GENERICARCH, SMP and HIGHMEM64G
> > allows NUMA to be selected but that configuration will not build
> > because it requires ACPI for the Summit NUMA support.
> 
> Good catch.    With X86_GENRICARCARCH perhaps NUMA should always be on
> or am I missing something with how it is supposed to work?  Shouldn't
> X86_GENRICARCARCH buy you the ablility to boot(correctly) on all the
> diffrent archs listed?

AFAIK not all Summit machines are NUMA, so maybe the flexibility is
needed.  e.g. some might want GENERICARCH without HIGHMEM64G.

-- 
Chuck
 "You can't read a newspaper if you can't read."  --George W. Bush

             reply	other threads:[~2006-07-07 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07 10:21 Chuck Ebbert [this message]
2006-07-07 18:16 ` Keith Mannthey
  -- strict thread matches above, loose matches on Subject: below --
2006-07-06 16:20 Chuck Ebbert
2006-07-06 18:43 ` Keith Mannthey

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=200607070623_MC3-1-C45A-2428@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=kmannth@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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®