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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F4194C433FE for ; Tue, 15 Mar 2022 01:17:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344235AbiCOBTC (ORCPT ); Mon, 14 Mar 2022 21:19:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43406 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344227AbiCOBTA (ORCPT ); Mon, 14 Mar 2022 21:19:00 -0400 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1845626D9; Mon, 14 Mar 2022 18:17:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1647307070; x=1678843070; h=message-id:subject:from:to:cc:date:in-reply-to: references:mime-version:content-transfer-encoding; bh=DWo909LPMfp/xcTS2ZhK17ummZUcNpAQabmYluiBYfs=; b=B5lESyfSk3KSU+uK8URBBXyWxnvm91nsZImSXHR3J9cFP9w5x5QTN4EY 8cB/4D90GHemEU0GhK6gXQEUFmrDbKwAfvCcMkPze1BnuXarWiqxgeco3 xM5MIVjRL9P/gXgdO7aro/8q5zpP+zKPDQqCblWG/DVYuzLB42xNVtivF 40JBfX7YdYPNC14CS5tkrk3KcxOGBmRtXO+T5wtcYzA32lzH+2OWd6q16 l2ji/dnY+hOCpnjJhLtoZLyLTkmzVKhgUYmD5MR4RJ45mQd7lL/g6NKE8 mL2OvbqKyEiLfQrwF1C7BaddsIFQNMTPZKt2Kx9OQ9lIouVEnoRPeEjm7 w==; X-IronPort-AV: E=McAfee;i="6200,9189,10286"; a="280951703" X-IronPort-AV: E=Sophos;i="5.90,181,1643702400"; d="scan'208";a="280951703" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Mar 2022 18:17:49 -0700 X-IronPort-AV: E=Sophos;i="5.90,181,1643702400"; d="scan'208";a="515673019" Received: from aholley-mobl1.amr.corp.intel.com (HELO khuang2-desk.gar.corp.intel.com) ([10.254.24.246]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Mar 2022 18:17:44 -0700 Message-ID: <0ffa85dbb54ddeecdbfdef3a22c077156268001b.camel@intel.com> Subject: Re: [RFC 0/3] Expose Confidential Computing capabilities on sysfs From: Kai Huang To: Isaku Yamahata , Alejandro Jimenez Cc: Dave Hansen , tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com, luto@kernel.org, peterz@infradead.org, x86@kernel.org, linux-kernel@vger.kernel.org, thomas.lendacky@amd.com, brijesh.singh@amd.com, kirill.shutemov@linux.intel.com, hpa@zytor.com, pbonzini@redhat.com, seanjc@google.com, srutherford@google.com, ashish.kalra@amd.com, darren.kenny@oracle.com, venu.busireddy@oracle.com, boris.ostrovsky@oracle.com, kvm@vger.kernel.org Date: Tue, 15 Mar 2022 14:17:42 +1300 In-Reply-To: <20220314224346.GA3426703@ls.amr.corp.intel.com> References: <20220309220608.16844-1-alejandro.j.jimenez@oracle.com> <8498cff4-3c31-f596-04fe-62013b94d7a4@intel.com> <746497ff-992d-4659-aa32-a54c68ae83bf@oracle.com> <20220314224346.GA3426703@ls.amr.corp.intel.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.4 (3.42.4-1.fc35) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > More concretely > - CPU feature (Secure Arbitration Mode: SEAM) as "seam" flag in /proc/cpuinfo In my current patchset we don't have "seam" flag in /proc/cpuinfo.   https://lore.kernel.org/kvm/cover.1647167475.git.kai.huang@intel.com/T/#m02542eb723394a81c35b9542b2763c783222d594 TDX architecture doesn't have a CPUID to report SEAM, so we will need a synthetic flag if we want to add. If userspace has requirement to use it, then it makes sense to add it and expose to /proc/cpuinfo. But so far I don't know there's any. Thanks -Kai