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 BB66CC433F5 for ; Thu, 31 Mar 2022 23:41:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243125AbiCaXnF (ORCPT ); Thu, 31 Mar 2022 19:43:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48754 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243114AbiCaXnE (ORCPT ); Thu, 31 Mar 2022 19:43:04 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C10B01AECB9; Thu, 31 Mar 2022 16:41:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1648770076; x=1680306076; h=message-id:subject:from:to:cc:date:in-reply-to: references:mime-version:content-transfer-encoding; bh=VF/NN9r92wUVinR+mO2GEHDVkuJEklr84R2QBIjD3NQ=; b=V1mTgb3+YFgpUulzF9jwtCrznJ0oWop9X+2kCeDICdhQE7Hu9tUe2XIT PSCcl0sXznGGsN4grDp8LTd899l2aswFq4gKiHVSWSGQRqN90DzlwXoCb UgV8vLYqQof+4BhF8ALDAY6FUvd3ms1kBEz/5OMLdjeXrn6aqKKZAdX8w ZwbGPnKQ1Ptu0aKpUV6vPw8oKUwhxsI+rWYsRsQ60S+f2Pe+KF+1Zqgf0 PZiRr8iqYHGMmyzIUwYiaH8IUJVDpH1442CEF6p9nZMt6PczQQAr7V5Bf LxrB1S62uy8kr9PpKC0zeOBI3OHy5ObXoj7d6FmJz4JptcEI+cDjzq6qP A==; X-IronPort-AV: E=McAfee;i="6200,9189,10303"; a="257570444" X-IronPort-AV: E=Sophos;i="5.90,225,1643702400"; d="scan'208";a="257570444" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Mar 2022 16:41:16 -0700 X-IronPort-AV: E=Sophos;i="5.90,225,1643702400"; d="scan'208";a="650494426" Received: from fpaolini-mobl2.ger.corp.intel.com (HELO khuang2-desk.gar.corp.intel.com) ([10.254.53.114]) by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Mar 2022 16:41:14 -0700 Message-ID: <945248cc85926fdbee65a2ad9165d86205973340.camel@intel.com> Subject: Re: [RFC PATCH v5 024/104] KVM: TDX: create/destroy VM structure From: Kai Huang To: Isaku Yamahata Cc: isaku.yamahata@intel.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Paolo Bonzini , Jim Mattson , erdemaktas@google.com, Connor Kuehl , Sean Christopherson Date: Fri, 01 Apr 2022 12:41:12 +1300 In-Reply-To: <20220331221207.GD2084469@ls.amr.corp.intel.com> References: <36805b6b6b668669d5205183c338a4020df584dd.1646422845.git.isaku.yamahata@intel.com> <20220331221207.GD2084469@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: kvm@vger.kernel.org On Thu, 2022-03-31 at 15:12 -0700, Isaku Yamahata wrote: > > It's really not clear why you need to know tdx_global_keyid in the context > > of > > creating/destroying a TD. > > TDX module mpas TDR with TDX global key id. This page includes key id assigned > to this TD.  Then, TDX modules maps other TD-related pages with the HKID. > TDR requires the TDX global key id for cache flush unlike other TD-related > pages. > I'll add a comment. Sorry I forgot this. Thanks. -- Thanks, -Kai