Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp4892783rwb; Mon, 21 Nov 2022 13:26:13 -0800 (PST) X-Google-Smtp-Source: AA0mqf54fR7mdi9vRgj6JwwmwMlfo+ZMhjBiwlc/7gh+d2Ed4zautHdKvjChrqEUc7RtIreAJkJu X-Received: by 2002:a17:906:fcc2:b0:78d:8b75:b161 with SMTP id qx2-20020a170906fcc200b0078d8b75b161mr17644952ejb.385.1669065973146; Mon, 21 Nov 2022 13:26:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669065973; cv=none; d=google.com; s=arc-20160816; b=bPdsMAvh2PsAsvQdwYdC4nAbdzQSfXgm9wjD7KSMhDbmphEKiKDuLedldvzC/1xwVO XWfphrD16aAPSaQ0nEPmYn7xoEPNXeBlbQ5aSjus904+/2T4VdR65hxNSBG7x36h1uuQ jSvyc5JYsICwWLx6C89ldCKx0BsAZlSG3ACZpFu2j0rxrlzeZeZYFgDjDb/xMSp3nBnu Vr4PIr+Ywjo/vSX6ooYKCSMFtSxF3mdcYu7cRzLO+UVE+K6MuC1IZl4aq7rxHCOpBnkE sEmaDzFfkBJM3Ixxy2ktaIsYiH/DfHGx2RSwVG1lNt2IYbO6JDuxuvys9WixcLmC9EeE Kppw== 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=4i7mUhWhAAiHEdfT3NI6LVUhTtEVbg+k3FSHBC6Epl8=; b=tAZzn1HG99sRkiHw6ZblM5yVvm/w6BS+hmZGeNBJoNn8CVhBdyK38Azx506v4zQ24a y7Lhk3d3qx1FQUmerOL+GPbFXk34ONt7AQ8BftlQLk+MnnZPsOQqUhrHsL306HMRqLt9 7HKfmgVa+puy3zjxBG94mUyElFlZ9pL4d5kKz+V+jFnlmp73ur76whGc3xpRmqkqCQ+u k80WWksiQSNIPMVyr6vVi+7s/L1gYJro53lt1A+9d8nuvFjWEDLcY5AjlGlEJxlQUx6W 49shmtOOiDnBkDN7yMXQSbihCts4ySSKPdwQgl8i13C8OCnxjfaoWOJ1meFiujCcyCRC 02oQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=BKxiwR0c; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w2-20020a056402268200b00468eee7250csi5026138edd.510.2022.11.21.13.25.49; Mon, 21 Nov 2022 13:26:13 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=BKxiwR0c; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230076AbiKUUio (ORCPT + 91 others); Mon, 21 Nov 2022 15:38:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46550 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230049AbiKUUik (ORCPT ); Mon, 21 Nov 2022 15:38:40 -0500 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E65B9B4F1E; Mon, 21 Nov 2022 12:38:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1669063119; x=1700599119; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=AngCEqZLkvJQBI60RTdDbXikONezRgG/ST493lmNsDQ=; b=BKxiwR0cp7OvyGqK5lbAwmulj5pjx3W8gO1bvJpmkRgUAc2lMcH3LXiS VVRsX2AcCaKoVZhyEw7W0qyl1nYsALTOzkQCoHl2lNzKf01V4nObTYnbS JwjcsBYTAdR8tNtEwTq5+ycTtaiyaMrgE3TtVVo8VHuvS64I8nBGuIkL9 o/ewRNghVxVt/wXUF4lMJ/icVT68dE7tkfiOM5iXvOmOBYMGj2WJm7jrA bZtyixjmNhNbCsiKGdlW+UTbHVqCTzkzhz91rDU3Fs9Vj7l/+HW0Te4GX RbfViETgqQvZivzVUCr80EangJcoq/q5xZxJb0L+3iwUoG9UlUGhEZ6Gg w==; X-IronPort-AV: E=McAfee;i="6500,9779,10538"; a="313688049" X-IronPort-AV: E=Sophos;i="5.96,182,1665471600"; d="scan'208";a="313688049" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Nov 2022 12:38:39 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10538"; a="886259322" X-IronPort-AV: E=Sophos;i="5.96,182,1665471600"; d="scan'208";a="886259322" Received: from ticela-or-327.amr.corp.intel.com (HELO [10.209.6.63]) ([10.209.6.63]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Nov 2022 12:38:37 -0800 Message-ID: <18323d11-146f-c418-e8f0-addb2b8adb19@intel.com> Date: Mon, 21 Nov 2022 12:38:36 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: [PATCH 1/6] x86/tdx: Support hypercalls for TDX guests on Hyper-V Content-Language: en-US To: Dexuan Cui , ak@linux.intel.com, arnd@arndb.de, bp@alien8.de, brijesh.singh@amd.com, dan.j.williams@intel.com, dave.hansen@linux.intel.com, haiyangz@microsoft.com, hpa@zytor.com, jane.chu@oracle.com, kirill.shutemov@linux.intel.com, kys@microsoft.com, linux-arch@vger.kernel.org, linux-hyperv@vger.kernel.org, luto@kernel.org, mingo@redhat.com, peterz@infradead.org, rostedt@goodmis.org, sathyanarayanan.kuppuswamy@linux.intel.com, seanjc@google.com, tglx@linutronix.de, tony.luck@intel.com, wei.liu@kernel.org, x86@kernel.org Cc: linux-kernel@vger.kernel.org References: <20221121195151.21812-1-decui@microsoft.com> <20221121195151.21812-2-decui@microsoft.com> From: Dave Hansen In-Reply-To: <20221121195151.21812-2-decui@microsoft.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_NONE autolearn=ham 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 11/21/22 11:51, Dexuan Cui wrote: > __tdx_hypercall() doesn't work for a TDX guest running on Hyper-V, > because Hyper-V uses a different calling convention, so add the > new function __tdx_ms_hv_hypercall(). Other than R10 being variable here and fixed for __tdx_hypercall(), this looks *EXACTLY* the same as __tdx_hypercall(), or at least a strict subset of what __tdx_hypercall() can do. Did I miss something? Another way of saying this: It seems like you could do this with a new version of _tdx_hypercall() (and all in C) instead of a new __tdx_hypercall().