[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b6361702-fa08-498b-a603-402ae8292102@intel.com>
Date: Mon, 28 Apr 2025 17:37:00 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Dan Williams <dan.j.williams@...el.com>, dave.hansen@...ux.intel.com
Cc: Kirill Shutemov <kirill.shutemov@...ux.intel.com>,
Vishal Annapurve <vannapurve@...gle.com>, Kees Cook <kees@...nel.org>,
stable@...r.kernel.org, x86@...nel.org,
Nikolay Borisov <nik.borisov@...e.com>, Naveen N Rao <naveen@...nel.org>,
Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
linux-coco@...ts.linux.dev, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, mpe@...erman.id.au,
suzuki.poulose@....com
Subject: Re: [PATCH v3 0/2] Restrict devmem for confidential VMs
On 4/28/25 15:48, Dan Williams wrote:
>> I guess arm and powerpc have cc_platform_has() so it's not _completely_
>> x86 only, either. Acks from those folks would also be appreciated since
>> it's going to affect them most immediately.
> I have added Suzuki and Michael for their awareness, but I would not say
> acks are needed at this point since to date CC_ATTR_GUEST_MEM_ENCRYPT is
> strictly an x86-ism.
>
> For example, the PowerPC implementation of cc_platform_has() has not been
> touched since Tom added it.
Ahh, good point. I was just grepping for cc_platform_has(), not
CC_ATTR_GUEST_MEM_ENCRYPT. Unless someone pipes up, I'd agree that acks
aren't required. Thanks for adding them to the cc though.
Powered by blists - more mailing lists