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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C37EBC433F5 for ; Thu, 28 Oct 2021 16:35:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 982DC6103C for ; Thu, 28 Oct 2021 16:35:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229755AbhJ1Qhf (ORCPT ); Thu, 28 Oct 2021 12:37:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60778 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229565AbhJ1Qhf (ORCPT ); Thu, 28 Oct 2021 12:37:35 -0400 Received: from mail.skyhub.de (mail.skyhub.de [IPv6:2a01:4f8:190:11c2::b:1457]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5A7EAC061570; Thu, 28 Oct 2021 09:35:08 -0700 (PDT) Received: from zn.tnic (p200300ec2f13a70087f257aa50e887e8.dip0.t-ipconnect.de [IPv6:2003:ec:2f13:a700:87f2:57aa:50e8:87e8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id C672A1EC066C; Thu, 28 Oct 2021 18:35:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1635438906; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=zh+2GNP02n/dF4/zNJ+FeGBfsbHiW2pUtoXXFtUgYqw=; b=Y7QXElCSiP3f5F2MygLvhg8uyJ3u/zL9/HdJ57Hu7Cm/OUTZNVgtdKS6tZWtNyEzE6WBPp QEiPgtn2mz1lnoDatHWqfAqLIT+lGq+I4TSTb3FG/WpgkAAA19rA3T7nCRZW/r2osYmO9a Wkee9fZnCgo4LXMmNwz0HHmvfYAmu/0= Date: Thu, 28 Oct 2021 18:35:03 +0200 From: Borislav Petkov To: Richard Hughes Cc: Martin Fernandez , Dave Hansen , linux-efi@vger.kernel.org, Platform Driver , Thomas Gleixner , Ingo Molnar , X86 ML , "H. Peter Anvin" , Dave Hansen , Andy Lutomirski , Peter Zijlstra , ardb@kernel.org, dvhart@infradead.org, andy@infradead.org, Greg KH , rafael@kernel.org, Daniel Gutson Subject: Re: [PATCH v2 0/5] [RFC] x86: Export information about hardware memory encryption to sysfs Message-ID: References: <20211027195511.207552-1-martin.fernandez@eclypsium.com> <8a8e0743-e54d-ec96-da4e-1d101b550274@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-efi@vger.kernel.org On Thu, Oct 28, 2021 at 05:03:20PM +0100, Richard Hughes wrote: > We've got Red Hat customers right now that are completely confused if > they have hardware capable of encrypted memory. We want to make it > part of a specification that can be passed to the people actually > purchasing the hardware. Sorry, you need to expand on that: part of what specification? How is this going to be run? How is the customer supposed to figure that out when she has the hardware? Why cannot this be a userspace program, script, tool, whatever? My questions are still unanswered. Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette