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, 14 May 2010 19:25:39 -0700 From: Mike Travis <travis@....com> To: "H. Peter Anvin" <hpa@...or.com> CC: Jesse Barnes <jbarnes@...tuousgeek.org>, Bjorn Helgaas <bjorn.helgaas@...com>, Mike Habeck <habeck@....com>, Ingo Molnar <mingo@...hat.com>, Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org, Jacob Pan <jacob.jun.pan@...el.com>, Tejun Heo <tj@...nel.org>, LKML <linux-kernel@...r.kernel.org>, Yinghai <yinghai.lu@...cle.com>, "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, Myron Stowe <myron.stowe@...com> Subject: Re: [Patch 1/1] x86 pci: Add option to not assign BAR's if not already assigned ... We're somewhat fortunate in that our Legacy I/O > devices are confined to those on the first blade, and all of these > other devices are on other blades (PCI segments 1+). By "somewhat" I meant we'd be way more fortunate without the legacy I/O devices at all! But hpa is right, 4 lines of assembler is way better than (900?) lines of C. My feeling is that if a CPU needs legacy i/o it should be built into the chip. HAH! ;-) The BIOS should just list the machine resources, in a "non-BIOS" way, (oh wait, that's ACPI! :*) Cheers! -- 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