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 1222222FE10 for ; Wed, 12 Mar 2025 08:23:15 +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=1741767798; cv=none; b=H0hSwEADhT681cJLjWc3xY4uoQaCf3gYJquuPtSVHCaSWGN7nevatgHbgo0Tf5ZNqR9a88KPf13qZy1Z0TlzQm6kt/QrHHwFmSsa6pzYcY/fsiBIwbILnTeRZkRPqKKNyO9PrqD6ARR7FVYmrdJmKOjii+uqXp7wdTPC01v5mcc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1741767798; c=relaxed/simple; bh=wmN9njbrOp06Jz992yjPTQLaFEbX0G2GM09PiUP7NWk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=XbByzICObX8XVv+5OQuGyym5xCoJ98n9C2MsbtjggDtnqUELC7/yV5dtPfABTSB4UdojNpIGVkG/37cdqnv+DWzT5h4FpqUvUXjdyWtUqCRXkpmDT2SiZEX226nl0dmyOGtnlHXZ7v0zXaPQHEE0sCSx7/eF1Wvg3JkxGv+gWjs= 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=n3VHjQBu; 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="n3VHjQBu" 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 94237454B4; Wed, 12 Mar 2025 09:23:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=8bytes.org; s=default; t=1741767794; bh=wmN9njbrOp06Jz992yjPTQLaFEbX0G2GM09PiUP7NWk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=n3VHjQBuUTP+I92Ank4nr/3PPHN2d8tbknI5Kvnm8XbaZMZ71E21jREnYwbb+3iUp FMsiq5ULV+RChd+NRG74reAv+/N3ODYCBq6RZjzN1Ltnjx+ztI9quwIHn+ObkK4myt B2nr1tBJaG35ArRCfkxfJwg2IHyEsxxeqXG1NJgjkLBlk2KmJYPQv3Vw3qgLBsKp0A 0b4nGbKUQcIu5QddwDGH/mLRZyqj/PP6GWG3CwjLVhPGpCncVIRiNMd/kK12vFV0EJ QMm/Ism4JsqVdVwKiTg4T0/W753h9tt3nCrJlRUrJhlGD+vCJ2jA+PlSmzhqgmagST XGVQAH3xRGNVw== Date: Wed, 12 Mar 2025 09:23:13 +0100 From: Joerg Roedel To: "Kirill A. Shutemov" Cc: Joerg Roedel , Alexey Gladkov , Borislav Petkov , =?iso-8859-1?Q?J=FCrgen_Gro=DF?= , "Alexey Gladkov (Intel)" , Dave Hansen , Ingo Molnar , x86@kernel.org, hpa@zytor.com, Tom Lendacky , Nikunj A Dadhania , linux-kernel@vger.kernel.org, Larry.Dewey@amd.com Subject: Re: [PATCH] x86/sev: Make SEV_STATUS available via SYSFS Message-ID: References: <20250310151154.GOZ88BOinZVkbYEx0w@fat_crate.local> <104b6d4f-2848-42f4-a134-3373d12d9424@suse.com> <29fa0d10-0d3d-47a0-8832-b2c7fc04f637@suse.com> <20250311110748.GCZ9AZhPYYAz-MXErv@fat_crate.local> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Wed, Mar 12, 2025 at 09:19:30AM +0200, Kirill A. Shutemov wrote: > TDX module information (version, supported features, etc) is crucial for > bug reporting. I think it makes sense to present it in sysfs. The SEV side presents this information via dmesg and /dev/sev, we can also talk about a place in sysfs for it. But the place to present host-side information is a separate discussion. Regards, Joerg