| 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: <4637D456.3040303@shaw.ca> Date: Tue, 01 May 2007 17:59:18 -0600 From: Robert Hancock <hancockr@...w.ca> To: Jesse Barnes <jesse.barnes@...el.com> Cc: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [PATCH] support PCI MCFG space on Intel i915 bridges Jesse Barnes wrote: > On Monday, April 30, 2007 4:20 pm Robert Hancock wrote: >>> Right, but you patch should obsolete this stuff anyway. I'll test >>> it out in the next few days. >> We likely still want this chipset-specific support, it will catch the >> case where the MCFG table lists a location which is reserved in ACPI >> but the chipset was actually programmed to a different location >> entirely, which I seem to remember someone mentioning was actually >> the case on some boards.. > > Yeah, I suppose that's true. So maybe your new checking code should > leverage the stuff in mmconfig-shared.c to check against the register > values like Olivier mentioned? The patch I sent takes the MCFG address from the chipset registers for known chipsets, or the ACPI MCFG table otherwise. Either way, it will verify that the memory range is reserved in ACPI. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from hancockr@...pamshaw.ca Home Page: http://www.roberthancock.com/ - 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