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 148D6C433FE for ; Mon, 21 Nov 2022 02:53:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229930AbiKUCxA (ORCPT ); Sun, 20 Nov 2022 21:53:00 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51896 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229919AbiKUCw5 (ORCPT ); Sun, 20 Nov 2022 21:52:57 -0500 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6531B2D1C8; Sun, 20 Nov 2022 18:52:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1668999175; x=1700535175; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=SZbXR0jnSRpjiZuLVZqtvWf/Wyu6UQpYVOi2XkaiVXc=; b=VQlyAF9pnCUSJR1QvXeg6ILLxzCoh6ZE8PbY4sQeUWAF8NPDKeNzMtK2 pkZZhD5bxBAIuIvTkUyOP8uLnjZz+OvRM+AB5SYSxjAlydScpEd83FJ5D ClZIy4q6+cMNXnsWZ+QJDkkVbWiMp4ZkRg0/duxgL/QCAvmgU9M8n0Ojz K6LjokEtW5QAMKH7rfWaeFokLExFjRsQ91CLyRog6lQRk3yf5NgPtZsub 67X2JnXLS5cWJhFRcALgAwIGKMCdZ1L1eGXhEDNcHhClqLkp4dUejDZAS 2Rbe/H97H9d2odLF64aH991Kx+U+i+JlVhBQWlbg7JEMBI+80GRc7V1Wn g==; X-IronPort-AV: E=McAfee;i="6500,9779,10537"; a="399747984" X-IronPort-AV: E=Sophos;i="5.96,180,1665471600"; d="scan'208";a="399747984" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Nov 2022 18:52:55 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10537"; a="969908459" X-IronPort-AV: E=Sophos;i="5.96,180,1665471600"; d="scan'208";a="969908459" Received: from mjcardon-mobl.amr.corp.intel.com (HELO [10.209.57.10]) ([10.209.57.10]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Nov 2022 18:52:53 -0800 Message-ID: <2eedfcff-e8c1-79af-63f4-c852af7b7e77@linux.intel.com> Date: Sun, 20 Nov 2022 18:52:53 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.2.2 Subject: Re: [PATCH v7 01/20] x86/tdx: Define TDX supported page sizes as macros Content-Language: en-US To: Kai Huang , linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: linux-mm@kvack.org, seanjc@google.com, pbonzini@redhat.com, dave.hansen@intel.com, dan.j.williams@intel.com, rafael.j.wysocki@intel.com, kirill.shutemov@linux.intel.com, ying.huang@intel.com, reinette.chatre@intel.com, len.brown@intel.com, tony.luck@intel.com, peterz@infradead.org, ak@linux.intel.com, isaku.yamahata@intel.com, chao.gao@intel.com, bagasdotme@gmail.com, sagis@google.com, imammedo@redhat.com References: From: Sathyanarayanan Kuppuswamy In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/20/22 4:26 PM, Kai Huang wrote: > +/* > + * TDX supported page sizes (4K/2M/1G). > + * > + * Those values are part of the TDX module ABI. Do not change them. It would be better if you include specification version and section title. -- Sathyanarayanan Kuppuswamy Linux Kernel Developer