| 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: <20070518010119.GB12088@linux-os.sc.intel.com> Date: Thu, 17 May 2007 18:01:19 -0700 From: "Siddha, Suresh B" <suresh.b.siddha@...el.com> To: "Eric W. Biederman" <ebiederm@...ssion.com> Cc: "Siddha, Suresh B" <suresh.b.siddha@...el.com>, mingo@...e.hu, ak@...e.de, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, "Zou, Nanhai" <nanhai.zou@...el.com>, "Mallick, Asit K" <asit.k.mallick@...el.com>, "Packard, Keith" <keith.packard@...el.com> Subject: Re: [patch] x86_64, irq: check remote IRR bit before migrating level triggered irq On Thu, May 17, 2007 at 05:30:13PM -0700, Eric W. Biederman wrote: > So why does any of this matter? > > My memory says that the ioapic state for sending irqs gets reset when we > unmask the irq. No. Atleast not on the platform we have tested. > If not I expect we can use the mask and edge, unmask and level > work-around from arch/i386/ioapic.c. That looks like it would > be less code, less error prone and easier to implement then the > current work around. hmm. We have to check and see if it can help. But ioapic spec doesn't say that the Remote IRR gets reset when the trigger mode changes. Not sure if we can apply the logic widely. thanks, suresh - 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