linux-kernel - Re: [PATCH] x86/sfi: fix ioapic gsi range

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]

Message-ID: <m18w6p5fwk.fsf@fess.ebiederm.org>
Date:	Tue, 08 Jun 2010 15:16:27 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Yuhong Bao <yuhongbao_386@...mail.com>
Cc:	<alan@...ux.intel.com>, <jacob.jun.pan@...ux.intel.com>,
	<arjan@...ux.intel.com>, <linux-kernel@...r.kernel.org>,
	<hpa@...or.com>, <mingo@...e.hu>, <feng.tang@...el.com>,
	<len.brown@...el.com>
Subject: Re: [PATCH] x86/sfi: fix ioapic gsi range

Yuhong Bao <yuhongbao_386@...mail.com> writes:

>> IRQ 14/15 is wrong for ATA today as its AHCI based on modern boxes
> Not to mention even before that there was native mode IDE!In fact, XP SP1 and later support switching to native mode IDE on BIOSes supporting it as described in this document:http://www.microsoft.com/whdc/device/storage/Native-modeATA.mspx

One of these days we may even get a system where the designers really
care for being simple and easy to use by software.  Where all devices
will be discoverable pci devices, and all irqs will be msi or msi-x.  No
ioapics, no irq routing tables, just nice simple standards conformant
hardware that we already support.

Until then I guess we get things like Moorestown which are effectively
a reinvention of ISA based systems, with different firmware, and
different non-standard ISA devices.  It isn't particularly fun to
smash yet another incompatible idea into the existing infrastructure.
The cleanups that introduce modularity, flexibility, and
maintainability for irq handling are barely keeping ahead of new
poorly integrated features that make the code brittle again.

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/