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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 14 Nov 2006 19:58:00 +0100 From: Andi Kleen <ak@...e.de> To: "Aaron Durbin" <adurbin@...gle.com> Cc: linux-kernel@...r.kernel.org, "Matthew Wilcox" <matthew@....cx> Subject: Re: [PATCH for 2.6.19] [6/9] x86_64: Update MMCONFIG resource insertion to check against e820 map. > I would like to know what others think regarding this area. I think it > would be a good > idea to converge the mmconfig.c implementations for both x86-64 and i386. Is > this not feasable for some reasons I am unaware of? It should lead to more > code reuse and allow for a more unified stance in how both architectures handle > the PCI memory-mapped config space. Yes, it should be done. But not 100% because x86-64 can use a much more efficient mapping scheme than i386. Probably with a mmconfig-common.c. When mmconfig.c was originally written there wasn't that much support code and the fork wasn't a issue, it just has grown over time as we work around more and more bugs. -Andi - 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