linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jack Steiner <steiner@sgi.com>, Andi Kleen <andi@firstfloor.org>,
	tglx@linutronix.de, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC 8/8] x86_64: Support for new UV apic
Date: Mon, 31 Mar 2008 11:42:09 -0700	[thread overview]
Message-ID: <86802c440803311142u4cbbdca9m830e86d46ad020af@mail.gmail.com> (raw)
In-Reply-To: <20080331123338.GA14636@elte.hu>

On Mon, Mar 31, 2008 at 5:33 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
>
>  * Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>
>  > On Sun, Mar 30, 2008 at 7:18 PM, Jack Steiner <steiner@sgi.com> wrote:
>  > > >
>  > >  > if the calling path like GET_APIC_ID is keeping checking if it is
>  > >  > UV box after boot time, that may not good.
>  > >  >
>  > >  > don't need make other hundreds of machine keep running the code
>  > >  > only for several big box all the time.
>  > >  >
>  > >  > YH
>  > >
>  > >
>  > >  I added trace code to see how often GET_APIC_ID() is called. For my
>  > >  8p AMD box, the function is called 6 times per cpu during boot. I
>  > >  have not seen any other calls to the function after early boot
>  > >  although I'm they occur under some circumstances.
>  >
>  > then it is ok.
>
>  yes - and even if it were called more frequently, having generic code
>  and having the possibility of an as generic as possible kernel image
>  (and kernel rpms) is still a very important feature. In that sense
>  subarch support is actively harmful and we are trying to move away from
>  that model.

regarding LinuxBIOS = coreboot + TinyKernel. some box need to use
64bit kernel, because 32 bit kernel could mess up the 64 bit
resources, and final kernel kexeced is 64 bit.

and TinyKernel need to stay with coreboot in MB flash rom, and that
flash is about 2M...

So hope it is easier to use MACRO to mask platform detect code out.

YH

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2008-03-31 18:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 18:21 Jack Steiner
2008-03-25 10:25 ` Andi Kleen
2008-03-25 17:56   ` Jack Steiner
2008-03-25 18:06     ` Andi Kleen
2008-03-26  2:23       ` Jeremy Fitzhardinge
2008-03-26  3:22         ` Glauber Costa
2008-03-26  7:29         ` Ingo Molnar
2008-03-26  7:38     ` Ingo Molnar
2008-03-30 20:23       ` Yinghai Lu
2008-03-30 21:03         ` Jack Steiner
2008-03-30 21:18           ` Andi Kleen
2008-03-30 23:29             ` Yinghai Lu
2008-03-31  2:18               ` Jack Steiner
2008-03-31  2:20                 ` Yinghai Lu
2008-03-31 12:33                   ` Ingo Molnar
2008-03-31 12:52                     ` Andi Kleen
2008-03-31 18:42                     ` Yinghai Lu [this message]
2008-03-31  6:48               ` Andi Kleen
2008-03-25 14:30 ` Ingo Molnar
2008-03-25 16:31   ` Jack Steiner
2008-03-26  3:24     ` Glauber Costa
2008-03-30 20:41 ` Yinghai Lu
2008-03-30 21:08   ` Jack Steiner
2008-03-30 23:24     ` Yinghai Lu

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=86802c440803311142u4cbbdca9m830e86d46ad020af@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --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