| 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
| ||
|
Message-ID: <86802c440802230055w6f36fefbs327738df3ff920bd@mail.gmail.com> Date: Sat, 23 Feb 2008 00:55:18 -0800 From: "Yinghai Lu" <yhlu.kernel@...il.com> To: "Andi Kleen" <andi@...stfloor.org> Cc: "Ingo Molnar" <mingo@...e.hu>, "Andrew Morton" <akpm@...ux-foundation.org>, "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] x86_64: make amd quad core 8 socket system not be clustered_box On Fri, Feb 22, 2008 at 11:10 AM, Andi Kleen <andi@...stfloor.org> wrote: > Yinghai Lu wrote: > > On Fri, Feb 22, 2008 at 11:07 AM, Andi Kleen <andi@...stfloor.org> wrote: > >> Yinghai Lu wrote: > >> > On Fri, Feb 22, 2008 at 11:00 AM, Andi Kleen <andi@...stfloor.org> wrote: > >> >> > so for that box [4, 0x23] still could be apic clustered? there is a hole [0,3].. > >> >> > >> >> I meant holes between the CPUs only, not including the IO-APICs. > >> >> > >> >> > >> >> > is their box using AMD cpu or not? > >> >> > >> >> Intel. AMD boxes don't really need clustered mode because they support > >> >> bigflat mode. > >> > > >> > So DMI or exclude AMD CPU? > >> > >> Just check for holes between the cpus as I suggested earlier > > > > how about their system that is not full populated with CPU? > > I would expect the APIC IDs to be continuous then. > so those box will have apic id hole even they are fully poluated with cpu...? 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/
Powered by blists - more mailing lists