| 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: <m11wkqh2q7.fsf@ebiederm.dsl.xmission.com> Date: Fri, 16 Feb 2007 02:27:12 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: "Natalie Protasevich" <protasnb@...il.com> Cc: lenb@...nel.org, "Andi Kleen" <ak@...e.de>, linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org Subject: Re: FW: [PATCH] i386: irq: Kill IRQ compression "Natalie Protasevich" <protasnb@...il.com> writes: > This routine actually renumbers gsi's. I don't think you can kill > ioapic_renumber_irq without bringing down ES7000 that have swapped > legacy/PCI ranges and are still out there. Moreover, mach-es7000 > purpose is to define and use the range swapper on the first ioapic. > Kernel still assumes legacy mapping having no overrides of that > extent. Perhaps the real fix is to have ACPI/MPS parsers to read the > actual pin/gsi information from the tables, which turned out pretty > difficult last time we tried. > --Natalie Yes I noticed, and you replied just before I send off an email explicitly asking you about this :) At first glance I thought it was that other piece of irq compression that showed up in arch/x86_64/io_apic.c but it appears arch/i386/io_apic.c does not have that. Anyway now all we have to do is bump up NR_IRQS and we should be good, patch in a moment. Eric - 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