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 73CFDC433EF for ; Tue, 26 Apr 2022 20:53:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1355174AbiDZU4f (ORCPT ); Tue, 26 Apr 2022 16:56:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33618 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344812AbiDZU4b (ORCPT ); Tue, 26 Apr 2022 16:56:31 -0400 Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 352604889D; Tue, 26 Apr 2022 13:53:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1651006398; x=1682542398; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=Yl/Zc0AZRDi45jgsJfvzClqb0ZXk0tbOP5iYoO41XQE=; b=mRLNP6R/p7L4XU3trXExAY5dJUd87aHdGOBGNITel4g3HWs1UPvJ1O3D hhDPs6fqukIdruoNikJXECg56i8Ur5eo76w9h9otvLrVWRC85xMOJNwpH wqnbgbYAsqNgO48Ku5jKFxibddR59/xM/Vcw86R5tm+RHdx229eDCUJnf h3NIz843Lhecg2ldX40sfaj3sjl8yjbiFS+uDKMfU+7njlOsJQ0E8UsEF EwYd0l5mmx8zqFhSkJwUJ932h8BuMYEJ5cLMKcb8IkHHSxnVD6KBnzxyw FX3WmZXLWuQIWF3l0wi+inI+SRpl+JVRcT5irIlYwcmPVN+uREyVFjEJ7 A==; X-IronPort-AV: E=McAfee;i="6400,9594,10329"; a="326207692" X-IronPort-AV: E=Sophos;i="5.90,292,1643702400"; d="scan'208";a="326207692" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Apr 2022 13:53:17 -0700 X-IronPort-AV: E=Sophos;i="5.90,292,1643702400"; d="scan'208";a="580152884" Received: from dsocek-mobl2.amr.corp.intel.com (HELO [10.212.69.119]) ([10.212.69.119]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Apr 2022 13:53:16 -0700 Message-ID: <104a6959-3bd4-1e75-5e3d-5dc3ef025ed0@intel.com> Date: Tue, 26 Apr 2022 13:56:05 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH v3 05/21] x86/virt/tdx: Detect P-SEAMLDR and TDX module Content-Language: en-US To: Kai Huang , linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: seanjc@google.com, pbonzini@redhat.com, len.brown@intel.com, tony.luck@intel.com, rafael.j.wysocki@intel.com, reinette.chatre@intel.com, dan.j.williams@intel.com, peterz@infradead.org, ak@linux.intel.com, kirill.shutemov@linux.intel.com, sathyanarayanan.kuppuswamy@linux.intel.com, isaku.yamahata@intel.com References: From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/5/22 21:49, Kai Huang wrote: > The P-SEAMLDR (persistent SEAM loader) is the first software module that > runs in SEAM VMX root, responsible for loading and updating the TDX > module. Both the P-SEAMLDR and the TDX module are expected to be loaded > before host kernel boots. Why bother with the P-SEAMLDR here at all? The kernel isn't loading the TDX module in this series. Why not just call into the TDX module directly?