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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id DE768EB64DD for ; Thu, 29 Jun 2023 01:01:33 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5B9238D0002; Wed, 28 Jun 2023 21:01:33 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 568C68D0001; Wed, 28 Jun 2023 21:01:33 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 431918D0002; Wed, 28 Jun 2023 21:01:33 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 30D358D0001 for ; Wed, 28 Jun 2023 21:01:33 -0400 (EDT) Received: from smtpin02.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 0C73040B52 for ; Thu, 29 Jun 2023 01:01:33 +0000 (UTC) X-FDA: 80953982466.02.A7C5FA1 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by imf12.hostedemail.com (Postfix) with ESMTP id 3F57440004 for ; Thu, 29 Jun 2023 01:01:29 +0000 (UTC) Authentication-Results: imf12.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=FEex3VnA; dmarc=pass (policy=none) header.from=intel.com; spf=none (imf12.hostedemail.com: domain of yuan.yao@linux.intel.com has no SPF policy when checking 192.55.52.115) smtp.mailfrom=yuan.yao@linux.intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1688000490; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=+uZllPu/GjCR4e2/9X5DmiYdUUx70V/ZdKrYHY4f124=; b=U+bImCHcv9KQh5X1YdR0aWLeRs4bwzV17cJz8g06ewwf4cdMSsFsM+kgT7KQjZBhpt/diI rDrqFX4T+P5KM6gocrGMaqstlNgzulY5AeE3VdJ2dbvm7VlbfYOTDXMBFat7OwVfFzDe0+ bxgv6IamI5EV0D2BK1vKrecrypaxjp0= ARC-Authentication-Results: i=1; imf12.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=FEex3VnA; dmarc=pass (policy=none) header.from=intel.com; spf=none (imf12.hostedemail.com: domain of yuan.yao@linux.intel.com has no SPF policy when checking 192.55.52.115) smtp.mailfrom=yuan.yao@linux.intel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1688000490; a=rsa-sha256; cv=none; b=ESkqDhKynuMbAQjSr1u05pMR5zF7epSxL1HJBWEaeEqTKoAJw1ahUSUA91chx16ji0NN1z u5VTqY2kTP8I4trzckU+OtAmVGEbkC/zCFabdKT6avxwPB+iR9UzqriR03ePcQ6fbnVIH9 L5DoNxTU/1kxyaP4n7YG+jDGd2ucFYg= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1688000490; x=1719536490; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=wvcp0oNxhAZF/jxUcax6I76yc5ZgM67abJCJcCMwEVU=; b=FEex3VnAh5/r34j0zpMGhopB3Ufc3rHAR3+ApnVyH8Gm4n1UKS1cXzMv hvIHSWIM6SXKPEXsnv4U7oMsePl6EUJ0C7+oUQxM0gQUO+flyIq4SlYbp ljvY4kHgeNOeCFRpV2KoOMS/7FeY4IzgargYMdkhQAUS5TYP2Tsrko4OY R7mvjJZYuOorUojKe8GQszn1auLoDyJstXRn0+Kcn+IHBGAyAVeXSJZcC 8OMoWBxV7uboW/mNGJqcah0JcBbhG2mxWniWArjFcQ59gpt5i7+NQzMDA IPPDnicvRf6yOyoPxSEr2lir8yrxKySoXE7cimlejOjCY6+wiixdqMzkF A==; X-IronPort-AV: E=McAfee;i="6600,9927,10755"; a="362038592" X-IronPort-AV: E=Sophos;i="6.01,167,1684825200"; d="scan'208";a="362038592" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Jun 2023 18:01:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10755"; a="1047600854" X-IronPort-AV: E=Sophos;i="6.01,167,1684825200"; d="scan'208";a="1047600854" Received: from yy-desk-7060.sh.intel.com (HELO localhost) ([10.239.159.76]) by fmsmga005.fm.intel.com with ESMTP; 28 Jun 2023 18:01:21 -0700 Date: Thu, 29 Jun 2023 09:01:20 +0800 From: Yuan Yao To: "Huang, Kai" Cc: "kvm@vger.kernel.org" , "Raj, Ashok" , "Hansen, Dave" , "david@redhat.com" , "bagasdotme@gmail.com" , "Luck, Tony" , "ak@linux.intel.com" , "Wysocki, Rafael J" , "linux-kernel@vger.kernel.org" , "Christopherson,, Sean" , "mingo@redhat.com" , "pbonzini@redhat.com" , "linux-mm@kvack.org" , "tglx@linutronix.de" , "kirill.shutemov@linux.intel.com" , "Chatre, Reinette" , "Yamahata, Isaku" , "nik.borisov@suse.com" , "hpa@zytor.com" , "peterz@infradead.org" , "Shahar, Sagi" , "imammedo@redhat.com" , "bp@alien8.de" , "Gao, Chao" , "Brown, Len" , "sathyanarayanan.kuppuswamy@linux.intel.com" , "Huang, Ying" , "Williams, Dan J" , "x86@kernel.org" Subject: Re: [PATCH v12 00/22] TDX host kernel support Message-ID: <20230629010120.odlfyf7ka7oexdls@yy-desk-7060> References: <20230628070418.6dky65allycok4us@yy-desk-7060> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20171215 X-Rspamd-Queue-Id: 3F57440004 X-Rspam-User: X-Rspamd-Server: rspam05 X-Stat-Signature: 7s7yghkmytb1i1mucemmrxpkfnbqu8fc X-HE-Tag: 1688000489-553194 X-HE-Meta: U2FsdGVkX18/uWsLH2+VLkYjWuF80iZ00EEVXDou0g3JPEwtYV227BMAjHZfYVWw4KFll8/bit/nygKMdEBXYB7NIRAI6usB9ty2ROOfnXVAet20yYE/FcKmGGz3QPx2kqwQaXJ1fCiirLNtKCoY7nalGmlXLO6XpCjPXpZ09s0ooStG4Ycj0oRfQ7TpWFnN+vAJXh0uAzV2QEAFBj9enfoBWSw5q3tOc8mXR6acn+gLyLb2GSdokvGR88RLAcVx6fbE4TxCotdwGV8UNWCmI6psCD0AQeGUHARJXrs2R4J81DoSHFGmHiIZUfhYEMVZIg3/qrX5wPxjX/g3eW7bF7gC34zDut1A9FHzok6EV+O1cb09ZQdnnZ4gkHhfm/NubyTeS2OPBAOPB4bZrnASDMvKTXW1/iTjPRwrUMIGlqxLrX+eBYmyvxs41Vz04WCeqphNPaFT5zbrbWYOUD1+jtxjoqfTu3UFJpp4Tt47Q/qLE4AhuPNOIvX4P5S8Ybgs4ciWvz2AW0mwCkaNeZp6bDfnJNLhmvw8Coz5HFrRp41IVPBXafgwRbsaQsEQEMRrL0Bwqy58ObmRBm5LySoMNE34z+O0aDprWjs6V6LT3/BiHwaACcpQ3H9+b7ayMvHMKXhYOdGAckL+jvfO3tI6RtHI7vLQCDzRIxqmV2wUgeDeOnzeseJ99mhwf4Elkwd08hUdchXpsd8ZTJ3Ck/Qp2thuBHZQsnMH0b0UBtxrFtAIBdrSQgCnqlijt+qAxfSFKUC5jAPHp+ScEwlpCO9Lnv8PU/AeggKIHJonOqJJ4DxhF7qTN5X0+mdldaxJaZG2d/QVAbmCRwezWmfiZIdijdymfVFf0eP2EZ2XCcZkzZH4hsjQfN7wvb58FZccvd7EkY3ik2qqO5BL7+SmtB8NhXB6Euy1F7vQWzuyIAq48kgM/+xdUocIwQ8MmnhKx+stTt4tIBcc6zcFmPuV7kg xgylxn8Q g+cjW+7vNF9bJxKC1FMAtbfa0R6f8eYlXxieFU4j2mnKm0V6E8niXn20lf64/Hcs+qSn9p3HMeyvlOFZvCbkyVmX7S1qtsB2MJ0jKXfnl5kRW9unUIHMcwLAwa6hqRaG9+DW1MQ9xAzhDwMSj6xBpcqeof/CuO8mBLW/w7FqjJDeHGs8= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, Jun 28, 2023 at 08:12:55AM +0000, Huang, Kai wrote: > > > > > > 2. CPU hotplug > > > > > > DX doesn't support physical (ACPI) CPU hotplug. A non-buggy BIOS should > > ^^ > > > > Need T here. > > Thanks! > > > > [...] > > > > 4. Memory Hotplug > > > > > > After the kernel passes all "TDX-usable" memory regions to the TDX > > > module, the set of "TDX-usable" memory regions are fixed during module's > > > runtime. No more "TDX-usable" memory can be added to the TDX module > > > after that. > > > > > > To achieve above "to guarantee all pages in the page allocator are TDX > > > pages", this series simply choose to reject any non-TDX-usable memory in > > > memory hotplug. > > > > > > 5. Physical Memory Hotplug > > > > > > Note TDX assumes convertible memory is always physically present during > > > machine's runtime. A non-buggy BIOS should never support hot-removal of > > > any convertible memory. This implementation doesn't handle ACPI memory > > > removal but depends on the BIOS to behave correctly. > > > > > > Also, if something insane really happened, 4) makes sure either TDX > > > > Please remove "4)" if have no specific meaning here. > > > > It means the mechanism mentioned in "4. Memory hotplug". Ah I see, it's fine to me, thanks. > >