Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp827659pxb; Fri, 22 Apr 2022 12:03:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw/8NIgbzmNLllwU1fgoB+xHLDm0qTI5NDQdWkD+bNLafZA/z0HfQbG7S55UQjqQj0juol+ X-Received: by 2002:a05:6808:13d2:b0:322:7571:79e with SMTP id d18-20020a05680813d200b003227571079emr3131449oiw.52.1650654208592; Fri, 22 Apr 2022 12:03:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650654208; cv=none; d=google.com; s=arc-20160816; b=dq7dl6ZgEthNT7KzIEVEpUHJ9ilTJ3eCxH2QMbP1o4gIg6n16SheVDHrEIe1EvKe7R B+BkwnVNi+EENs/P9nqNuvnj7QUip5UwJiEHkx1XRPUdiY4X5I0YiimKZrqfniMkt0pS LG+7SCT+6CSD+il+KCfqMmpSkUVsS+tVpj/QropotSSVIi72n0P9IHeCTLqgxb8/tUwY yccEndLlP9EmsnPBwS5KF6NOl9j/9VrOMGu955BZkFyU43KxAVpL3KC/qloq+Sg2IAfs XvMn0wQvyCf/GhBe8IoBpVTIlINzx3ETE4MTjwIThEahMtHgyFo8T6jsQM68CUCP2GTb BEYg== 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=RjOgLFqTRdsPqqG1i2yyJD/ZBYyy5tnlnWm2bbE/nYQ=; b=Pq9Hy1UCicKxCsmfOXST8HKCUscs3gK4U49gSvs9z5ccMeW2O+nnFvQ32G6UR9s9cf 7RFqjAVMqaQmFpAYSU5eKfW2QKLoQKl4SxPwK1I+jy8q7yNRCXp2rVcT8NOTyFywTsEi o2SLpCBdkUL4IzItgWGANBj7iNAGnZG+ttldAbv48ZKugw3Pvz2vqaYj0xJVj8HBMlbw JSO4MP/3IFbj32050+fcTSHiYihfja/eHVgMu7/gL7ZVKHD0eOVd7In9eM8jW4LhTGK8 SVUpSQv6fF07leHwWL9b/5EGWvyIGXmE7BSsv5adQ1SmSs346n3iU5tBzn0JK6fyQf3d xD1w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=UZluPZIN; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 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. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id n1-20020a4ac701000000b003249598a7a7si5261979ooq.70.2022.04.22.12.03.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Apr 2022 12:03:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=UZluPZIN; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 977571968A3; Fri, 22 Apr 2022 11:24:18 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1359762AbiDTHcW (ORCPT + 99 others); Wed, 20 Apr 2022 03:32:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49800 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1359719AbiDTHcS (ORCPT ); Wed, 20 Apr 2022 03:32:18 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5C9B43B2AC; Wed, 20 Apr 2022 00:29:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650439773; x=1681975773; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=+2VkkaHgs7Bi4lmS3LREzrgtsND2nPSs2jyfSDUHHGU=; b=UZluPZINbjZCeCKdtOV5ANkT+aU0cv1b24ntmZoknuYw8hqim/iNpULc MNhHhovbHKJgrWCRnRq0CAm/hfY3qC+jwgfs2tI0uA1r29zk5m7erIc4D VWQIsuBdANH6hV3Ub5OFX16LbupJSUaiE42YJNsTG1p+X6kUsMgBaLaQJ dUTl0atcHYsmCVG5BYaZoZkEHKwJMMzj1A0oV1Wyu2XcKmeRwKyi++bCl +aLB4G2+JTCCqsGSbrGfYGgQ+8rDHVVlKvjU88A6OKx/7t5L01f8urPWK P+0pfy03Cd/h17GCO1778ODdMuBhw4bdtY38Kh7vWCaXef0PNPD/C/aaS A==; X-IronPort-AV: E=McAfee;i="6400,9594,10322"; a="261565065" X-IronPort-AV: E=Sophos;i="5.90,275,1643702400"; d="scan'208";a="261565065" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Apr 2022 00:29:33 -0700 X-IronPort-AV: E=Sophos;i="5.90,275,1643702400"; d="scan'208";a="562007675" Received: from ktuv-desk2.amr.corp.intel.com (HELO [10.212.227.192]) ([10.212.227.192]) by fmsmga007-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Apr 2022 00:29:32 -0700 Message-ID: Date: Wed, 20 Apr 2022 00:29:31 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.7.0 Subject: Re: [PATCH v3 03/21] x86/virt/tdx: Implement the SEAMCALL base function Content-Language: en-US To: Kai Huang , linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: seanjc@google.com, pbonzini@redhat.com, dave.hansen@intel.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, isaku.yamahata@intel.com References: <1c3f555934c73301a9cbf10232500f3d15efe3cc.1649219184.git.kai.huang@intel.com> From: Sathyanarayanan Kuppuswamy In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,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/19/22 9:16 PM, Kai Huang wrote: > On Tue, 2022-04-19 at 07:07 -0700, Sathyanarayanan Kuppuswamy wrote: >> >> On 4/5/22 9:49 PM, Kai Huang wrote: >>> SEAMCALL leaf functions use an ABI different from the x86-64 system-v >>> ABI. Instead, they share the same ABI with the TDCALL leaf functions. >> >> TDCALL is a new term for this patch set. Maybe add some detail about >> it in ()?. >> >>> > > TDCALL implementation is already in tip/tdx. This series will be rebased to it. > I don't think we need to explain more about something that is already in the tip > tree? Since you have already expanded terms like TD,TDX and SEAM in this patch set, I thought you wanted to explain TDX terms to make it easy for new readers. So to keep it uniform, I have suggested adding some brief details about the TDCALL. But I am fine either way. > > -- Sathyanarayanan Kuppuswamy Linux Kernel Developer