From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.8bytes.org (mail.8bytes.org [85.214.250.239]) by smtp.subspace.kernel.org (Postfix) with ESMTP id DAF0C1D514E for ; Wed, 12 Mar 2025 16:19:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=85.214.250.239 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741796345; cv=none; b=elluxTAmpKwF5aXWE3NNBRTVK9TfnjQ0bQGTcjkJO5iKsukjIBCyrxMs8jCG+thyPpesrXMIuJitnLeDoJas5ATQ2lLkFBcaNPPmKYfICEIj9Od3foYq79BLutiYcANh1iWIXajdsPcCem83whtwoVLyw1CHXZ6gEdekOKuDZqs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741796345; c=relaxed/simple; bh=r5wW3O7Nnkvs71M/SLdq386LsVv5kb/pJTQyMSmxX7c=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=VblLtmvc6OIcBqikTc/mxynoWECzDYqEKhSJaQ6gSuqLkojW1Y1FdbuNfwNB9e+Mk4o7QKhxEMCHFJlo+Mkoab8gjM+5dYpa3+6uTauKEzE20R7YE1c3ZQqVql+xYcQCLGKt5GUAwNv8uHPE/QYOLXQmpSj4C/Rq3JIsqn5p3pY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=8bytes.org; spf=pass smtp.mailfrom=8bytes.org; dkim=pass (2048-bit key) header.d=8bytes.org header.i=@8bytes.org header.b=pV3kuEbb; arc=none smtp.client-ip=85.214.250.239 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=8bytes.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=8bytes.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=8bytes.org header.i=@8bytes.org header.b="pV3kuEbb" Received: from 8bytes.org (p4ffe03ae.dip0.t-ipconnect.de [79.254.3.174]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.8bytes.org (Postfix) with ESMTPSA id BC68345742; Wed, 12 Mar 2025 17:19:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=8bytes.org; s=default; t=1741796342; bh=r5wW3O7Nnkvs71M/SLdq386LsVv5kb/pJTQyMSmxX7c=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pV3kuEbbx74gmsu4xnQaEbkMf6NVwuMeR0+cqxHb8z16w9rNqF2rPdjGeT75ll+qK Kx6VrHkBCBJJqz++GyYBhhiyJGKdggkAbG3QgjXu/JwYcqMxCLvB22R/uZOUuO/QUb cHzko8fC0Iva21PpnhKhjGRhiC906h/f0MmwaZMXvaqloTxRDBdOFSEsVE9oTVod6c xFNkZNb/DLuUxIP/isWmOuPt+s8Aiu2TTET2zvSKZy6Oto1CYNO/o83UQZRq25UPOr nfWnQWDbaz+J+fPZcXiPLlGTLVOAI4iP443X8JFJkHoln+jBExxJkuHm70yrI4vksq EitZqTSOX0uYg== Date: Wed, 12 Mar 2025 17:19:01 +0100 From: Joerg Roedel To: Dave Hansen Cc: Joerg Roedel , x86@kernel.org, hpa@zytor.com, Tom Lendacky , Nikunj A Dadhania , Larry.Dewey@amd.com, linux-kernel@vger.kernel.org, linux-coco@lists.linux.dev, Juergen Gross , kirill.shutemov@linux.intel.com, alexey.gladkov@intel.com Subject: Re: [PATCH 2/2] x86/sev: Make SEV_STATUS available via SYSFS Message-ID: References: <20250312144107.108451-1-joro@8bytes.org> <20250312144107.108451-3-joro@8bytes.org> <862e626a-3d4b-40c0-b1b1-6a51b30dcd22@intel.com> Precedence: bulk X-Mailing-List: linux-coco@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <862e626a-3d4b-40c0-b1b1-6a51b30dcd22@intel.com> On Wed, Mar 12, 2025 at 09:04:14AM -0700, Dave Hansen wrote: > Let's draw this out to its natural conclusion. There are also a bunch of > TDX attributes that tell you about the capabilities of the VM and the > TDX module. > > Should we have: > > /sys/devices/system/cpu/tdx/tdx_attributes > > which just dumps out the raw register values that come back from the > TDCALL? Then we'll go write a tdxguest tool to parse those values. If I remember correctly the goal of the VirTEE project (where the snpguest tool lives) is to come up with a combined teeguest tool. This will serve as a vendor- and architecture-independent frontend for the various kernel interfaces for confidential computing (configfs-tsm, sysfs-attributes, ...). So yes, my expectation is that this tool will understand the raw values returned from the TDCALL, as long as they are architectural. But let me think a bit more about a solution that takes care of the tooling and the human requirements. Regards, Joerg