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 X-Spam-Level: X-Spam-Status: No, score=-5.4 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6CC30C4338F for ; Wed, 4 Aug 2021 23:00:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4E50061107 for ; Wed, 4 Aug 2021 23:00:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234169AbhHDXAg (ORCPT ); Wed, 4 Aug 2021 19:00:36 -0400 Received: from mga03.intel.com ([134.134.136.65]:17519 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229479AbhHDXAf (ORCPT ); Wed, 4 Aug 2021 19:00:35 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10066"; a="214059107" X-IronPort-AV: E=Sophos;i="5.84,295,1620716400"; d="scan'208";a="214059107" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Aug 2021 16:00:21 -0700 X-IronPort-AV: E=Sophos;i="5.84,295,1620716400"; d="scan'208";a="512261135" Received: from bguvendi-mobl.amr.corp.intel.com (HELO skuppusw-mobl5.amr.corp.intel.com) ([10.212.99.93]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Aug 2021 16:00:20 -0700 Subject: Re: [PATCH v5 04/12] x86/tdx: Add protected guest support for TDX guest To: Sean Christopherson Cc: Dave Hansen , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Peter Zijlstra , Andy Lutomirski , Peter H Anvin , Tony Luck , Dan Williams , Andi Kleen , Kirill Shutemov , Kuppuswamy Sathyanarayanan , x86@kernel.org, linux-kernel@vger.kernel.org References: <20210804181329.2899708-1-sathyanarayanan.kuppuswamy@linux.intel.com> <20210804181329.2899708-5-sathyanarayanan.kuppuswamy@linux.intel.com> <9c576f24-e6de-f816-623d-408a4a2ae747@intel.com> <4f28fe6e-a8ce-e444-51db-d0eb564eca8f@linux.intel.com> From: "Kuppuswamy, Sathyanarayanan" Message-ID: Date: Wed, 4 Aug 2021 16:00:18 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/4/21 3:42 PM, Sean Christopherson wrote: > What other possible use case is there for invoking tdx_prot_guest_has() beyond > running as a TDX guest? If it were e.g. intel_prot_guest_has() then I would at > least understand the code, if not agree with the sub-optimal approach, but as is > it makes no sense. Yes. I think his original intention is to implement intel_prot_guest_has() in arch/x86/kernel/cpu/intel.c and then call tdx_prot_guest_has() from it. But since we have no other use cases, we have called tdx_prot_*() directly here. Boris, how do you want to proceed? Do you want me to implement intel_prot_guest_has() or change comparison log to TDX specific? > > Given amd_prot_guest_has(), my guess is Boris intended intel_prot_guest_has()... -- Sathyanarayanan Kuppuswamy Linux Kernel Developer