Received: by 2002:a05:6602:2086:0:0:0:0 with SMTP id a6csp4435438ioa; Wed, 27 Apr 2022 03:57:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzQA0DirfyW3q+/7iAfyIVXuoidOlXFwzAyWq6Ntv91kHz1wfT+EFlvSucEZuRz22PV8E1S X-Received: by 2002:a17:90a:31cf:b0:1c9:f9b8:68c7 with SMTP id j15-20020a17090a31cf00b001c9f9b868c7mr43784487pjf.34.1651057051450; Wed, 27 Apr 2022 03:57:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651057051; cv=none; d=google.com; s=arc-20160816; b=xlIwxs/YI4lqLgvkTicbI9+X6VMkX4hswwnCubcvMF68iluAdtRvWvUJapUwwwLSG1 PUKtMPeU+mTaySjFfEs+mU9Dd165mtw7wWgW5bGxEb7qTZ7xKjNI3sj/dJUS7TUdBgyC zFznZyPCBQ0QnotOIxFRUndSG36SB5Ae8za74mpJSkQEpUEnbSiztYDLUvAHY3CrIlqh Cb6dkursHqhumvfyE7ofhnUFbgChF1OZ+j1p1YUYpd3VJmKoPCbhpJSo2sBtVXRRPuN8 vGKiUA6bX8h7im2NlXf4AXiXlYOKNEgG+VnQ3mKsKMdIIr7EWG5rT+Tmfx/MHXAFKZ3s Bwtg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=BmWa2EWprM4I0+9OlUSR16R8N/b8HSXboLXYLmnzK68=; b=fHoaiWwM35FB+oeCtxOWqtviMvdjrrZYaOHN5m+ChgYygqVR5r1WbLu+xiaZozJtGp zVpzi6ULNKi68FJcn3qvfL+pIlOcwxwLlhwt8+gZlCWrYFzhtHLXK2/0sWvoAlg+0n10 DHq5Gl2HeM9CdMxQzW2pVtvozbbh34x8c5cGs1S2FoDQxeGRc2hfVE4h5VuVXCagGcFe IajWwemenZ2ajjJNp0fSAvGP6uwe2WIi7Y26x/yKKCiLVjTVOR8QIfT5yJun/0O/Gy4Q zzDEhq/y3WthADunqsOhygjAfyKgKjup7Etp2TPJQzKLMnp6wIFVpxhsPlk+CIFHYbSt ZtBQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="mRLNP6R/"; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id 3-20020a630303000000b003ab1c70fe88si1264002pgd.24.2022.04.27.03.57.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Apr 2022 03:57:31 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="mRLNP6R/"; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 7CCE180BFE; Wed, 27 Apr 2022 03:04:38 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1355172AbiDZU4e (ORCPT + 99 others); Tue, 26 Apr 2022 16:56:34 -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 X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,RDNS_NONE,SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net 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?