linux-kernel - Re: [PATCH] - UV fix for size of hub mappings

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]

Date:	Sat, 27 Sep 2008 22:02:14 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jack Steiner <steiner@....com>
Cc:	tglx@...utronix.de, linux-kernel@...r.kernel.org,
	"H. Peter Anvin" <hpa@...or.com>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [PATCH] - UV fix for size of hub mappings


* Jack Steiner <steiner@....com> wrote:

> > x2apic support is available in tip/master, so it would be nice to 
> > glue UV to generic x2apic support properly and remove duplication 
> > and fixmes.
> 
> Good point. I'll send the fixes to you early next week. Recently, I've 
> been focused on a distro release which is still waiting for the x2apic 
> code. However, I don't need to wait to fix this upstream...

great!

> > For example, do we really need apic_x2apic_uv_x, or could we use 
> > apic_x2apic_cluster?
> 
> Unfortunately, we really need a uv genapic. IPIs on large UV systems 
> can't use an x2apic model. Because of the size of our large systems, 
> APICIDs in the cpu MSRs are not globally unique. We have a special 
> feature in the UV chipset that must be used for on large systems for 
> IPIs. Small & medium sized system can and do use the x2apic genapic.

not a problem really - it's not really complex or intrusive, we just 
want to make sure all unnecessary duplication is eliminated.

	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/