linux-kernel - Re: [RFC 8/8] x86_64: Support for new UV apic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <86802c440803311142u4cbbdca9m830e86d46ad020af@mail.gmail.com>
Date:	Mon, 31 Mar 2008 11:42:09 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Jack Steiner" <steiner@....com>,
	"Andi Kleen" <andi@...stfloor.org>, tglx@...utronix.de,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC 8/8] x86_64: Support for new UV apic

On Mon, Mar 31, 2008 at 5:33 AM, Ingo Molnar <mingo@...e.hu> wrote:
>
>
>  * Yinghai Lu <yhlu.kernel@...il.com> wrote:
>
>  > On Sun, Mar 30, 2008 at 7:18 PM, Jack Steiner <steiner@....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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/