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 378DFC433F5 for ; Fri, 4 Feb 2022 12:27:45 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id B94296B0072; Fri, 4 Feb 2022 07:27:44 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id B43D96B0073; Fri, 4 Feb 2022 07:27:44 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A0C0D6B0074; Fri, 4 Feb 2022 07:27:44 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0099.hostedemail.com [216.40.44.99]) by kanga.kvack.org (Postfix) with ESMTP id 8DB256B0072 for ; Fri, 4 Feb 2022 07:27:44 -0500 (EST) Received: from smtpin20.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 4773F98C00 for ; Fri, 4 Feb 2022 12:27:44 +0000 (UTC) X-FDA: 79105023648.20.1503653 Received: from mail-yb1-f170.google.com (mail-yb1-f170.google.com [209.85.219.170]) by imf16.hostedemail.com (Postfix) with ESMTP id CC66E18000A for ; Fri, 4 Feb 2022 12:27:43 +0000 (UTC) Received: by mail-yb1-f170.google.com with SMTP id v190so1958248ybv.4 for ; Fri, 04 Feb 2022 04:27:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eclypsium.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=E3CkuQfRDLa6yHQhfPXnQaFzdcsQFUeKCKzEBzUj/zQ=; b=TLYrEShYRf1FgVk7hHjObf4x7nd8odacHjXXRpq7yKoaHl2d4cJ8VON/yE+OgjlACN Deh2m4l0lPgbHURrAba9Ro14SwwCHOG+0Nv/hlUJcn2mcThUbfxE1IEO+W36tUg3MKW8 n9FacUSOrGV/A/mXTq2Us80gIm1AwkidrArvgQCcxcpwcOfU251m8g9w7lWjvl5mpD4u SfanAQlOPlFgouyo1XEy0iTabqHr8/mV6qhVD2e86dRrwMGK8LqcKRLW9ShW+qjxuzZP Qoqi5BjNrLiMA0YsO4/3q0qFyxsOyT2LoygR0q9mALUNNnZ+Tl4jGIva6c7WrbMUHXYo vjIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=E3CkuQfRDLa6yHQhfPXnQaFzdcsQFUeKCKzEBzUj/zQ=; b=CLX0GWS0AuBXPP3eAQmM17EBgAjY3Afz+ve0nkSSrslB8d4y8K4Y61TULvg9pK+dLZ VyVZ6QQAfLJ6615tE320J1sidSEOWZNOQqs5PwvcYlXmLHgzmigEST26pyzK0FVgGYe0 On0o79crDYEdwfz+6UhOuL2kMCod4E8fsMZq3XeH/VPkkjxKsPlXD06XxuoxJGg7VX2U /k5GMX6Ez6HuomRJhP1Yo74P8V8H8ETNwsnCpYaRoKDX6p0v2lB07fa6ipLCIqigZcxD ET/2CObuZF/Mis40Lvq0biP4Xnlo8tpQexPcYGH/PliPFAZx3MwlWNQq5ZqpxBY6uPIX YCSg== X-Gm-Message-State: AOAM531zj8lWMhdu9TchqtnAkoHk295S8Ifemj8TxIDG+kCG+ciKnr97 y+aFHtZ30oo9Wjd2cQfURkk1hEB4A+xbyYq6xEKOag== X-Google-Smtp-Source: ABdhPJy0uUYEV/PGiz45GMg1qGGeLJ0gKE2zXBEUciykyjrQIx6iwM/SZFE1OhdU1ZXjgjR2rQwIB4Km1IhUiy5ChGA= X-Received: by 2002:a81:6605:: with SMTP id a5mr2526438ywc.510.1643977662982; Fri, 04 Feb 2022 04:27:42 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a81:1756:0:0:0:0:0 with HTTP; Fri, 4 Feb 2022 04:27:42 -0800 (PST) In-Reply-To: References: <20220203164328.203629-1-martin.fernandez@eclypsium.com> <20220203164328.203629-7-martin.fernandez@eclypsium.com> From: Martin Fernandez Date: Fri, 4 Feb 2022 09:27:42 -0300 Message-ID: Subject: Re: [PATCH v6 6/6] drivers/node: Show in sysfs node's crypto capabilities To: Mike Rapoport 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 Content-Type: text/plain; charset="UTF-8" X-Rspam-User: nil X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: CC66E18000A X-Stat-Signature: 37awfxj6x1oamuiqfuw3gd8ehg7kitn9 Authentication-Results: imf16.hostedemail.com; dkim=pass header.d=eclypsium.com header.s=google header.b=TLYrEShY; dmarc=pass (policy=quarantine) header.from=eclypsium.com; spf=pass (imf16.hostedemail.com: domain of martin.fernandez@eclypsium.com designates 209.85.219.170 as permitted sender) smtp.mailfrom=martin.fernandez@eclypsium.com X-HE-Tag: 1643977663-785588 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000064, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: 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?