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 E76EFC433F5 for ; Wed, 1 Dec 2021 13:22:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245726AbhLANZz (ORCPT ); Wed, 1 Dec 2021 08:25:55 -0500 Received: from mga05.intel.com ([192.55.52.43]:51079 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234027AbhLANZy (ORCPT ); Wed, 1 Dec 2021 08:25:54 -0500 X-IronPort-AV: E=McAfee;i="6200,9189,10184"; a="322701747" X-IronPort-AV: E=Sophos;i="5.87,278,1631602800"; d="scan'208";a="322701747" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Dec 2021 05:22:33 -0800 X-IronPort-AV: E=Sophos;i="5.87,278,1631602800"; d="scan'208";a="540824436" Received: from jelopeza-mobl1.amr.corp.intel.com (HELO khuang2-desk.gar.corp.intel.com) ([10.254.29.181]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Dec 2021 05:22:29 -0800 Date: Thu, 2 Dec 2021 02:22:27 +1300 From: Kai Huang To: Sean Christopherson Cc: isaku.yamahata@intel.com, Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H . Peter Anvin" , Paolo Bonzini , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , erdemaktas@google.com, Connor Kuehl , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, isaku.yamahata@gmail.com Subject: Re: [RFC PATCH v3 00/59] KVM: X86: TDX support Message-Id: <20211202022227.acc0b613e6c483be4736c196@intel.com> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Tue, 30 Nov 2021 18:51:52 +0000 Sean Christopherson wrote: > On Wed, Nov 24, 2021, isaku.yamahata@intel.com wrote: > > - drop load/initialization of TDX module > > So what's the plan for loading and initializing TDX modules? Hi Sean, Although I don't quite understand what does Isaku mean here (I thought loading/initializing TDX module was never part of TDX KVM series), for this part we are working internally to improve the quality and finalize the code, but currently I don't have ETA of being able to send patches out, but we are trying to send out asap. Sorry this is what I can say for now : (