linux-kernel - Re: [PATCH V9 0/5] map GHES memory region according to EFI memory map

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]

Date:	Mon, 3 Aug 2015 17:23:54 +0100
From:	Matt Fleming <matt@...eblueprint.co.uk>
To:	Will Deacon <will.deacon@....com>
Cc:	"Jonathan (Zhixiong) Zhang" <zjzhang@...eaurora.org>,
	Matt Fleming <matt.fleming@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	"x86@...nel.org" <x86@...nel.org>,
	"tony.luck@...il.com" <tony.luck@...il.com>,
	"ard.biesheuvel@...aro.org" <ard.biesheuvel@...aro.org>,
	"fu.wei@...aro.org" <fu.wei@...aro.org>,
	"al.stone@...aro.org" <al.stone@...aro.org>,
	"bp@...en8.de" <bp@...en8.de>,
	"rjw@...ysocki.net" <rjw@...ysocki.net>,
	"lenb@...nel.org" <lenb@...nel.org>,
	"ying.huang@...el.com" <ying.huang@...el.com>,
	Catalin Marinas <Catalin.Marinas@....com>,
	"leif.lindholm@...aro.org" <leif.lindholm@...aro.org>,
	"hanjun.guo@...aro.org" <hanjun.guo@...aro.org>,
	"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
	"linaro-acpi@...ts.linaro.org" <linaro-acpi@...ts.linaro.org>,
	"vgandhi@...eaurora.org" <vgandhi@...eaurora.org>,
	"timur@...eaurora.org" <timur@...eaurora.org>
Subject: Re: [PATCH V9 0/5] map GHES memory region according to EFI memory map

On Mon, 03 Aug, at 12:26:58PM, Will Deacon wrote:
> 
> I guess this is all going via Matt's tree? I'm happy to take the new
> memory type in arch/arm64/ if there's nothing currently queued, but I
> suspect it makes more sense for it to stay together.

Right, it probably does make sense to take this through a single tree.

I'm still waiting for the ACPI folks to chime in on whether this series
makes sense, and in particular I'd like to hear from people that have
touched ghes.c in the past.

Rafael, Boris?

-- 
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/