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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080331123338.GA14636@elte.hu>
Date:	Mon, 31 Mar 2008 14:33:38 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yhlu.kernel@...il.com>
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


* 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.

It is very nice that Jack has managed to make UV a generic platform 
instead of a subarch - and i'd encourage all future PC platform 
extensions to work via that model. The status of current PC 
subarchitectures is the following:

 - mach-visws: obsolete. We could drop it today - it's been years since 
                         i saw real VISWS bugreports.

 - mach-voyager: obsolete.

 - mach-es7000: on the way out - latest ES7000's are generic.

 - mach-rdc321x: it's being de-sub-architectured. It's about one patch 
                 away from becoming a non-subarch.

so we are just a few patches and a few well-directed voltage spikes away 
from being able to remove the subarch complication from x86 altogether 
;-)

	Ingo
--
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/