| 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: Wed, 17 Dec 2008 22:47:19 -0700 From: Grant Grundler <grundler@...isc-linux.org> To: Kenji Kaneshige <kaneshige.kenji@...fujitsu.com> Cc: Grant Grundler <grundler@...isc-linux.org>, Manu Abraham <abraham.manu@...il.com>, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org Subject: Re: MSI messages On Mon, Dec 15, 2008 at 04:07:53PM +0900, Kenji Kaneshige wrote: > Grant Grundler wrote: > >> To put it short: i am wondering how i should read the MSI messages. > > > > The "message" is actually mapped to an the interrupt vector by the core > > generic interrupt handling code in the kernel. > > > > A "GSI" (Generic Sys Interrupt?) is associated with each entry in > > the MSI-X table. Driver then calls request_irq() to bind an interrupt > > handler to each GSI. So the driver never directly sees the "message". > > > > I think "GSI (Global System Interrupt)" is for identifying the I/O > APIC pin among multiple I/O APICs. Maybe you wanted to mean the > interrupt number managed by kernel (frequently called "IRQ")? I thought "GSI" and "kernel interrupt number" are equivalents. But I could easily be confusing the terms here. If "GSI" is only used for identifying APIC input lines, then that's not right term. > Or am I misunderstanding something? You probably understand it better than I do. :) thanks, grant -- 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