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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F069BC4332F for ; Tue, 7 Dec 2021 19:46:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236623AbhLGTta (ORCPT ); Tue, 7 Dec 2021 14:49:30 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36486 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236516AbhLGTt3 (ORCPT ); Tue, 7 Dec 2021 14:49:29 -0500 Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 51220C061574 for ; Tue, 7 Dec 2021 11:45:58 -0800 (PST) Received: by mail-yb1-xb2b.google.com with SMTP id d10so569030ybn.0 for ; Tue, 07 Dec 2021 11:45:58 -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=2MSneKG+T5ZjFsWvdBHkKcc61yLnH/4zmInamMFTcOc=; b=XRkVTCiWO1xz/EgHSVzeCjqGeOiyHM0C+EN8gqsD/GqXB68KIB5RbhVg6sQb4LCb3u MRNmBwVVRaoAZ/Q8jvhNx0e/VxiN53KcjnypA1l69bDxHGLdgaPSd2GEhJowXsz53FKl I+zyjV3nz4SgF+4McKTXS6Nj32UMfk04IS1TsLBkMasy3mRiOg+KHMPOh4QpyZJIwsRq 0ZyNf2090Jdx/gL/0XHDt5WWeVpPXHocZB1Ad8FOBYIdcEGqn1l6V2KsGrvXH2ApiBjs ArsNfqlOy7/hXZXncjsZCbJHFeVHPFLaUAE6TNcwsPZ45P3l49H/Dp4cQZHVTqKb8Mfa avhg== 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=2MSneKG+T5ZjFsWvdBHkKcc61yLnH/4zmInamMFTcOc=; b=CclgdJW4Kk/QI3OMCuHVJCiPSp82X8Xh4v1lE2z8Fxr5Tf96I+MD2GZVavI6Q6eJxz ODbvbk1iXPUM6Te+LISviPOmAgZocsWiL+sunCeyQdqRUN/tTQTfS+7j4hMb7P2AXasY RX45UB6cxPMMBJUbl8MrH5cR4MXk1WMC/cRhZ8rmioH0B5NtY54akU4CIJfElmHCKMet pt3uMXxON3bqfs/sO7PDVBLHaUX/769cUc+PxPz9LBds0LBaz7KNFHWTcY84QVaTLZq3 MVxG8P1D2fNvQUvIV8c6Uey49A2SC+qTdLbjtJeP6UfAgCIK3GjFSZCPvsQAxpVIhpkw xmyw== X-Gm-Message-State: AOAM533EgkJlP9AXN/qHV56PF9DG0fOSB5IMljlTioqCgPRe6FHOg+kT kRXwZoNyl5+fUIu1ItWetybJnfrnsL96h2Dfs8Jhlg== X-Google-Smtp-Source: ABdhPJyMqHWSV5GGCftCDu/HHVqZSiWmTiUYcfhsLUySuKeO9UuAqLyCDwSql+GLxl0eiomj1NdDabqRlTah2chxdy8= X-Received: by 2002:a25:c8c3:: with SMTP id y186mr53620558ybf.20.1638906357546; Tue, 07 Dec 2021 11:45:57 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a0d:c906:0:0:0:0:0 with HTTP; Tue, 7 Dec 2021 11:45:56 -0800 (PST) In-Reply-To: References: <20211203192148.585399-1-martin.fernandez@eclypsium.com> From: Martin Fernandez Date: Tue, 7 Dec 2021 16:45:56 -0300 Message-ID: Subject: Re: [PATCH v3 0/5] x86: Show in sysfs if a memory node is able to do encryption To: Mike Rapoport Cc: Richard Hughes , 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, alex.bazhaniuk@eclypsium.com, alison.schofield@intel.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/7/21, Mike Rapoport wrote: > Hi Richard, > > On Mon, Dec 06, 2021 at 07:58:10PM +0000, Richard Hughes wrote: >> On Sun, 5 Dec 2021 at 06:04, Mike Rapoport wrote: >> > On Fri, Dec 03, 2021 at 04:21:43PM -0300, Martin Fernandez wrote: >> > > fwupd project plans to use it as part of a check to see if the users >> > > have properly configured memory hardware encryption capabilities. >> > I'm missing a description about *how* the new APIs/ABIs are going to be >> > used. >> >> We're planning to use this feature in the Host Security ID checks done >> at every boot. Please see >> https://fwupd.github.io/libfwupdplugin/hsi.html for details. I'm happy >> to answer questions or concerns. Thanks! > > Can you please describe the actual check for the memory encryption and how > it would impact the HSI rating? > > I wonder, for example, why did you choose per-node reporting rather than > per-region as described in UEFI spec. Some time ago we discussed about this and concluded with Dave Hansen that it was better to do it in this per-node way. This is the archive of the relevant discussion: http://lkml.iu.edu/hypermail/linux/kernel/2006.2/06753.html