linux-kernel - Re: [PATCH 2/2] x2apic, cluster: use all the members of one cluster specified in the smp_affinity mask for the interrupt desintation

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]

Date:	Tue, 22 May 2012 21:39:22 +0400
From:	Cyrill Gorcunov <gorcunov@...nvz.org>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
Cc:	Ingo Molnar <mingo@...nel.org>, agordeev@...hat.com,
	yinghai@...nel.org, linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH 2/2] x2apic, cluster: use all the members of one cluster
 specified in the smp_affinity mask for the interrupt desintation

On Tue, May 22, 2012 at 10:21:15AM -0700, Suresh Siddha wrote:
> On Tue, 2012-05-22 at 09:04 +0200, Ingo Molnar wrote:
> > * Suresh Siddha <suresh.b.siddha@...el.com> wrote:
> > 
> > > If the HW implements round-robin interrupt delivery, this 
> > > enables multiple cpu's (which are part of the user specified 
> > > interrupt smp_affinity mask and belong to the same x2apic 
> > > cluster) to service the interrupt.
> > 
> > Could/should we do something similar for regular APICs as well? 
> > They too support masks and LowestPrio delivery - and doing that 
> > will increase test coverage rather significantly.
> 
> Existing logical flat xapic mode already takes advantage of this today.

Suresh, should not we tune up es7000_cpu_mask_to_apicid code to return
apicid with a cluster number and ORed logical apicid part as done for
x2apic, or the way it resturns apicid now was done by a purpose?

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