From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 14B2CC433EF for ; Fri, 4 Feb 2022 13:38:14 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 6B2156B0072; Fri, 4 Feb 2022 08:38:14 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 63BE56B0073; Fri, 4 Feb 2022 08:38:14 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 4B4976B0074; Fri, 4 Feb 2022 08:38:14 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0197.hostedemail.com [216.40.44.197]) by kanga.kvack.org (Postfix) with ESMTP id 324126B0072 for ; Fri, 4 Feb 2022 08:38:14 -0500 (EST) Received: from smtpin21.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id E3FFB987B3 for ; Fri, 4 Feb 2022 13:38:13 +0000 (UTC) X-FDA: 79105201266.21.E59BC4F Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by imf25.hostedemail.com (Postfix) with ESMTP id 3DA89A0004 for ; Fri, 4 Feb 2022 13:38:13 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 71160B83734; Fri, 4 Feb 2022 13:38:11 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B8CC3C004E1; Fri, 4 Feb 2022 13:38:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1643981890; bh=ADsLWrDPUHmAqFOd35u++j4ThxtN9Oz6/99IGv9oiic=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=iEBVddxxEGZ8Z/cP1AXKMf6eHPQ9U6NMkiaKUe7OdNODPCCunKqCWLvufroq8oqo+ IgLv5eRgIdm/TmPaDZ8qWYCU57rA6tK3EIHQqzn5BgEP1BNl/UXF26nhcm5Wcm3Kns /dLBxNDC+S2C+0uUZEianRM9pmGbgYOvQzcGCRuR+Jsyywhf3eMVTaMzjGuZX6NSRn R3DkFb2EXoy6v5eAuyUYxWq2eLHkQ8mwiPMSGb3qf1ccmUtTjBRbhFjhJ2zYtPuQqi Zaxm9eILt6xbeMwAyuMOxYY21i1+ya9QM4ylXTdD6PCs+OnA91cqLXuFafI9zy+XjR oYuJbZz7DegHQ== Date: Fri, 4 Feb 2022 15:37:56 +0200 From: Mike Rapoport To: Martin Fernandez Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org, platform-driver-x86@vger.kernel.org, linux-mm@kvack.org, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com, ardb@kernel.org, dvhart@infradead.org, andy@infradead.org, gregkh@linuxfoundation.org, rafael@kernel.org, akpm@linux-foundation.org, daniel.gutson@eclypsium.com, hughsient@gmail.com, alex.bazhaniuk@eclypsium.com, alison.schofield@intel.com, keescook@chromium.org Subject: Re: [PATCH v6 6/6] drivers/node: Show in sysfs node's crypto capabilities Message-ID: References: <20220203164328.203629-1-martin.fernandez@eclypsium.com> <20220203164328.203629-7-martin.fernandez@eclypsium.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Server: rspam11 X-Rspamd-Queue-Id: 3DA89A0004 X-Stat-Signature: d85ibpmr3iqgxecnsia7mxio9wzj3wag Authentication-Results: imf25.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=iEBVddxx; dmarc=pass (policy=none) header.from=kernel.org; spf=pass (imf25.hostedemail.com: domain of rppt@kernel.org designates 145.40.68.75 as permitted sender) smtp.mailfrom=rppt@kernel.org X-Rspam-User: nil X-HE-Tag: 1643981893-734394 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Fri, Feb 04, 2022 at 09:27:42AM -0300, Martin Fernandez wrote: > On 2/4/22, Mike Rapoport wrote: > > On Thu, Feb 03, 2022 at 01:43:28PM -0300, Martin Fernandez wrote: > >> +Description: > >> + This value is 1 if all system memory in this node is > >> + marked with EFI_MEMORY_CPU_CRYPTO, indicating that the > > > > It didn't jump at me at previous postings, but other architectures won't > > necessary have EFI_MEMORY_CPU_CRYPTO marking crypto-capable memory. > > > > How about > > > > This value is 1 if all system memory in this node is capable of being > > protected with the CPU's memory cryptographic capabilities. It is 0 > > otherwise. > > On EFI architectures with value corresponds to EFI_MEMORY_CPU_CRYPTO. > > > > > > Yes, sounds good to me. > > Is there other architecture with something similar to this? Or are you > thinking on the possibility of such architecture? AFAIU, s390 and powerpc have memory encryption capabilities, I don't know the details though. -- Sincerely yours, Mike.