Received: by 2002:a05:7412:da14:b0:e2:908c:2ebd with SMTP id fe20csp1900784rdb; Mon, 9 Oct 2023 06:37:25 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGt5HOduGl2b5ckGbDiB+tS5ZKstsL6zjforCTslwhWBYYMgcnO87ouH0g5GNc5Ch/5WNwg X-Received: by 2002:a17:902:e74b:b0:1bb:6875:5a73 with SMTP id p11-20020a170902e74b00b001bb68755a73mr16905545plf.2.1696858644947; Mon, 09 Oct 2023 06:37:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1696858644; cv=none; d=google.com; s=arc-20160816; b=hCvMhyGk7Lv87FuFQ9WAuhch3gdso5yCjphvb8Rl53a0Gc1Hy5dGZKHh9iQm0ADZPe FxJD//qtGJUwYA4qJwMlwYaUn563HJO58ZMaGWMDGHZHPPWhZfza/cKhlz6phFdQ/VlJ KF34jIAbcTHRzMrj8qyNmfV1+c1+p5rKqPOmspMo9GqKNAIFgUlDPmQJWiZfTmwU/dyt iqEv9xiJp7alXn5iArHfeMwg2tFQsp9SMscLMwZiV6mKfZocbl5kIT6Q8NrcCpImiruE ovmbVhkbPt0Zv2bHxyFMBUapFZOf3nys7BQHrrnWMOypFHGM5KZMKIxazQtghIwsHH7f 6YOw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=zxUKoIModwjEujDbqzC8Mlpl+ZdsE4Wr49IWlgzdZxk=; fh=Wj9+p36r7zx82WCRUFQeEck5Cay/tY7jxS/3C72tb4Q=; b=sHIfkby6HJW070HbYxQjW1BO6DTlY+8UuoVK+2q92bFy7ToN1MAl2qphx88c39Fmgb Cs4DAOj5YUnP/Bg8GFymVQDYqeW939aZhQBZ5qwXE+QnD3wvYD6lpR9T9sT+hohq9uDA 3lXgYYtm2So6ypYjZSAumBPp4nFxCcJ1EJcUDiLE0NqPHQIXhTj4qsM01sOhpCLuJNHu xlqFHCp/SEJ4OGCN9dqAHnx+gC3hc6ZwwG8M9gf70J5LyWObX/AxW2r0nozUBAI9fUD4 WrsL+le7krm4U6iCmoQTdIUYpFF9SjvboYb+bBUD9WA1wZdx1wrSQcKgdoOinAFcfGrr H8Wg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=fhPvEhQA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 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 groat.vger.email (groat.vger.email. [23.128.96.35]) by mx.google.com with ESMTPS id m17-20020a170902c45100b001c3f6dbe2bdsi5834931plm.105.2023.10.09.06.37.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Oct 2023 06:37:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) client-ip=23.128.96.35; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=fhPvEhQA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 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 out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by groat.vger.email (Postfix) with ESMTP id A67B28075B0A; Mon, 9 Oct 2023 06:37:18 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at groat.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377215AbjJINhH (ORCPT + 99 others); Mon, 9 Oct 2023 09:37:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52664 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1377218AbjJINhF (ORCPT ); Mon, 9 Oct 2023 09:37:05 -0400 Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CB28A9D for ; Mon, 9 Oct 2023 06:37:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1696858623; x=1728394623; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=pTBhh0Z/eWz4qUWI59Hqv+z4l97YfU9wayl/EFDoxSw=; b=fhPvEhQAQLfkY2E5WldCWKNKM1gIUsX1g7uxFCccOTNgdjSj8J2gsy+J PthyFCv2RRuIXHlGJ6QXCczZSe4NUkI8491xHNgROZz2eqG5W1w8a7Ocb ZV1ENcoqTm6tJxYUT0Y6RJNjqogew97U07mmffD2huAKh0VndQsha10VC bQG7mhMLXfYN4tTytruoOYmyojdpYIjhDbgQgYevqq0H/wf1P+kQr2RxB dQTDzMcFM5/9kgGnVY8GveP9GYyQ4HPqxfdWi4Tr17ROsYu4xRbJEbV31 T43W69kq2gjnpQ9AYBic30RhtSue2YcQh9OijrVfaFY08/GUl9/cr9xrJ A==; X-IronPort-AV: E=McAfee;i="6600,9927,10858"; a="450645438" X-IronPort-AV: E=Sophos;i="6.03,210,1694761200"; d="scan'208";a="450645438" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Oct 2023 06:37:03 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10858"; a="756721610" X-IronPort-AV: E=Sophos;i="6.03,210,1694761200"; d="scan'208";a="756721610" Received: from ahuge-mobl.ger.corp.intel.com (HELO box.shutemov.name) ([10.252.40.233]) by fmsmga007-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Oct 2023 06:36:58 -0700 Received: by box.shutemov.name (Postfix, from userid 1000) id E967510A196; Mon, 9 Oct 2023 16:36:55 +0300 (+03) Date: Mon, 9 Oct 2023 16:36:55 +0300 From: "Kirill A. Shutemov" To: Baoquan He Cc: Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "Rafael J. Wysocki" , Peter Zijlstra , Adrian Hunter , Kuppuswamy Sathyanarayanan , Elena Reshetova , Jun Nakajima , Rick Edgecombe , Tom Lendacky , kexec@lists.infradead.org, linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH 00/13] x86/tdx: Add kexec support Message-ID: <20231009133655.3aqi4kwx7wtqgqtm@box.shutemov.name> References: <20231005131402.14611-1-kirill.shutemov@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=2.8 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_SBL_CSS,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on groat.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (groat.vger.email [0.0.0.0]); Mon, 09 Oct 2023 06:37:19 -0700 (PDT) X-Spam-Level: ** On Mon, Oct 09, 2023 at 07:49:35AM +0800, Baoquan He wrote: > On 10/05/23 at 04:13pm, Kirill A. Shutemov wrote: > > The patchset adds bits and pieces to get kexec (and crashkernel) work on > > TDX guest. > > > > They bring kexec support to the point when we can start the new kernel, > > but it will only be able to use single CPU. It should be enough to cover > > the most common case: crashkernel. > > Not sure if this question has been raised and answered in the past. Please > forgive my bad memory if it has. The one cpu is fine to kdump kernel most > of time, while we enable all CPUs by default when kexec rebooting. And kdump > kernel with multiple cpu is allowed too. Wondering if there's plan to > support the multiple cpu on TDX in the future. Sorry, I didn't update this part of cover letter properly, but the last patch of the patchset makes possible to kexec with multiple CPUs and the 2nd kernel will see them all. It requires support on BIOS side, otherwise we fallback to single CPU kexec. -- Kiryl Shutsemau / Kirill A. Shutemov