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
| ||
|
Date: Fri, 01 Aug 2008 18:36:52 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Yinghai Lu <yhlu.kernel@...il.com> CC: "Eric W. Biederman" <ebiederm@...ssion.com>, Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>, Dhaval Giani <dhaval@...ux.vnet.ibm.com>, Mike Travis <travis@....com>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 00/16] dyn_array and nr_irqs support v2 Yinghai Lu wrote: >> Sorry I was referring to the MSI-X source vector number which is a 12 >> bit index into an array of MSI-X vectors on the pci device, not the >> vector we receive the irq at on the pci card. > > cpu is going to check that vectors in addition to vectors in IDT? No, but the mapping from MSI-X vectors to -> {CPU, IDT} is arbitrary, as the MSI(-X) address and data registers contain the target CPU and destination vector, respectively. However, we may have to manage the mappings directly, to re-use IDT entries and provide interrupt balancing. -hpa -- 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