| 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: Tue, 23 Jun 2015 10:50:33 +0100 From: Matt Fleming <matt@...eblueprint.co.uk> To: Borislav Petkov <bp@...en8.de> Cc: "Zhang, Jonathan Zhixiong" <zjzhang@...eaurora.org>, Matt Fleming <matt.fleming@...el.com>, Thomas Gleixner <tglx@...utronix.de>, fu.wei@...aro.org, al.stone@...aro.org, tony.luck@...il.com, rjw@...ysocki.net, lenb@...nel.org, ying.huang@...el.com, linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH V3 4/4] acpi, apei: use EFI memmap to map GHES memory On Mon, 22 Jun, at 06:11:31AM, Matt Fleming wrote: > > Right, but see my previous comment about x86 discarding a bunch of > attributes for memory regions because the kernel "knows better". > > And in most places, yes, the kernel really does know better. But this > APEI case is special because irrespective of what the kernel says we > want to be compatible with the firmware's memory map. > > And we don't have an API for that. Maybe what we want is a new PAGE_* protection that is compatible with any firmware mappings? That'd be nice because we wouldn't have to introduce a whole new API for this GHES case and ioremap_* could do whatever it wanted under the hood. Thougts? -- Matt Fleming, Intel Open Source Technology Center -- 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