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 D8BF4C83013 for ; Wed, 2 Jul 2025 10:05:42 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 405E76B00E2; Wed, 2 Jul 2025 06:05:42 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 38EAA6B00E3; Wed, 2 Jul 2025 06:05:42 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 255FA6B00E4; Wed, 2 Jul 2025 06:05:42 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 106766B00E2 for ; Wed, 2 Jul 2025 06:05:42 -0400 (EDT) Received: from smtpin20.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 97D2155B63 for ; Wed, 2 Jul 2025 10:05:41 +0000 (UTC) X-FDA: 83618892882.20.1860317 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.19]) by imf29.hostedemail.com (Postfix) with ESMTP id 794CA12000A for ; Wed, 2 Jul 2025 10:05:38 +0000 (UTC) Authentication-Results: imf29.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=aGTeaalE; spf=none (imf29.hostedemail.com: domain of kirill.shutemov@linux.intel.com has no SPF policy when checking 198.175.65.19) smtp.mailfrom=kirill.shutemov@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1751450739; 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=yFPDO8wn9lPZIZ1zJElVQIsypTh71/0txTFL0JN7GiY=; b=bE9MjbvlFQcX7c7gHxmO4287H97Hz3Q0RBOXEAzqlqcfX9cgNljg3J28w0XOf9OsFTiLe2 +uHBIsuHtQdT+gZXVr5yAIChnmkjw1cbDiSTd15eVlfkxOP8gb61OwzZG/+j0H/Fo0kd7m BUaF9Hx9izCFaaS3aRpipSWK7vPaJsc= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1751450739; a=rsa-sha256; cv=none; b=yQ3AQcR3Zeiduddr0wsX3++hF34cNNp4TOZAXlqcduF4th4kTze2Du1qlRinfXo2zmZRGK MxKbsb3BFG5mqLfXdERQTTQuWypf2aeiHZ4oW1uHNBgFgfcb0FdAXQpzT0l1TLZqjQw8ld L8eFI7h/Oih2/6mPZcoFlJo7H+PPPzU= ARC-Authentication-Results: i=1; imf29.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=aGTeaalE; spf=none (imf29.hostedemail.com: domain of kirill.shutemov@linux.intel.com has no SPF policy when checking 198.175.65.19) smtp.mailfrom=kirill.shutemov@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1751450738; x=1782986738; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=Bw4Y/IgagKvBTqG1QoK2vY6ZG8eSZpTmBIYDJdyKhEo=; b=aGTeaalEm21+fEB4v9Qq8y/o5jUNBjzRJiaafiKjjpIx9nxC1KYVKbEm 5QbZ7wZPCCyUpYzvfhg+DzT29IKMzdYGxxsdeaSAtWhJBL+moR2INjplp HR0myeejTyxHqSDUVbHFFFHFSQF8vJ5KdB0ZXAdWmGPgwP3qUUW7lHbso Kmjpsy9fQbSA5LzEIOf61vdCCFxhT8+XRNdLhH0hncswU5oY0TchXn1o2 DLi/thN+aOj92wL0Zt9OeYKeO+IyPeZyUjIHD1Dxzdx0Bsn8gO5Puxy/t x+qdQSj9I37/WHXHyS7gto91UFjBsYU1RbuUSWTQuyv/2Z0n3x8muDsW1 A==; X-CSE-ConnectionGUID: USZY36GKQ+6XYwKAsc4dYQ== X-CSE-MsgGUID: CNw8mxGDRoOmaIxtwUxVDg== X-IronPort-AV: E=McAfee;i="6800,10657,11481"; a="53605749" X-IronPort-AV: E=Sophos;i="6.16,281,1744095600"; d="scan'208";a="53605749" Received: from orviesa008.jf.intel.com ([10.64.159.148]) by orvoesa111.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Jul 2025 03:05:36 -0700 X-CSE-ConnectionGUID: 5CGaxxggTDqWWnHrDvXjCQ== X-CSE-MsgGUID: e6lTZ57AR666aCfvszHJlw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.16,281,1744095600"; d="scan'208";a="154516220" Received: from black.fi.intel.com ([10.237.72.28]) by orviesa008.jf.intel.com with ESMTP; 02 Jul 2025 03:05:25 -0700 Received: by black.fi.intel.com (Postfix, from userid 1000) id 689101E0; Wed, 02 Jul 2025 13:05:23 +0300 (EEST) Date: Wed, 2 Jul 2025 13:05:23 +0300 From: "Kirill A. Shutemov" To: Dave Hansen Cc: Andy Lutomirski , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , Peter Zijlstra , Ard Biesheuvel , "Paul E. McKenney" , Josh Poimboeuf , Xiongwei Song , Xin Li , "Mike Rapoport (IBM)" , Brijesh Singh , Michael Roth , Tony Luck , Alexey Kardashevskiy , Alexander Shishkin , Jonathan Corbet , Sohil Mehta , Ingo Molnar , Pawan Gupta , Daniel Sneddon , Kai Huang , Sandipan Das , Breno Leitao , Rick Edgecombe , Alexei Starovoitov , Hou Tao , Juergen Gross , Vegard Nossum , Kees Cook , Eric Biggers , Jason Gunthorpe , "Masami Hiramatsu (Google)" , Andrew Morton , Luis Chamberlain , Yuntao Wang , Rasmus Villemoes , Christophe Leroy , Tejun Heo , Changbin Du , Huang Shijie , Geert Uytterhoeven , Namhyung Kim , Arnaldo Carvalho de Melo , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCHv8 04/17] x86/cpu: Defer CR pinning setup until after EFI initialization Message-ID: <2n2knq4wkzyfr35udpxawgnc4ykk7s77yavu3crnzf77wjaj4c@njyscphln4gl> References: <20250701095849.2360685-1-kirill.shutemov@linux.intel.com> <20250701095849.2360685-5-kirill.shutemov@linux.intel.com> <841a200e-bcf0-4488-acbd-c00396a9ccd2@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <841a200e-bcf0-4488-acbd-c00396a9ccd2@intel.com> X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: 794CA12000A X-Stat-Signature: wwbbs65f3iq3uiefgdc3pjkknry59gaz X-Rspam-User: X-HE-Tag: 1751450738-115166 X-HE-Meta: U2FsdGVkX18f2uHzupMjRPLAuJFNuyQptdgjLAhCnbHmOWIouiGdeEF+CvNKcYVF+g/vZlly8sfLHIxgXsPmWPYxk0mfE59b/GjczNWy0QxBWcWFxFetePGYrC5m4NLrOS8LTA5swzAqW0PfK5p4lMRwlQLQgosI4vCAtjEbnTe2a84iDMYkfadGb9rlafmodwDpT1j+vkaq8fP/Y8EH4zUCXn+HidJ6U61wO6WHvtP7Cu1SZkzvQxjYBrNQjcdHe5/L2YiiG8Nq/kJKJlE6eqSdLXSupFsiZVRM0AknSIAwDBBfGdEQWUZnQTDgfYIpqLEG3Pjx25Ins8yjEdnjPkoGIsBBaM2aOdzm8FLpiEdwd/3knKHzBXnW1a+nNPZZuV/+gRYVC/BSOzJ45ItPy9IU5z/4yUU206vPlAD0W1A41rGTjMeqP5zQd7Z1fZ6BiBQz+XJZGOa5lzPQMvwwFPnt1j8GFqNgQ+3UTS4nfTmqTV8ZtZaBU3QXnMkbDZUpE90/zWsZuXcHPMJYe2WSlyZM5NGuq97saWdumL2TmEu41LjxxjMzDVga/tQoWelH2/lEwrbn9/zBJ4ZsH9F+lxfd2II4uldpJ6U5/GWkhqc8c1rfolKWxCovOqeuw0mVjZ5oH5hPZOY+i9cRc+sn7CO5tdEUpZDV/lemMT8JBl8Dv6YYGDDKF6C1ESzBdlS/mLdegkvQucVwsEVqUqrgbW6dJweXB+SgbT7U+qtIVcgTsaxW+zkO/1snDO6VM0kNDeJ3fepFOhDmZQFmjK+c5GtLfvu/TxwFAOhkiV1hAZdT7yUYnxgR7dmrN4sWxRfuxJAxZmNm/aXvD65OQTvy/eHdoDlHrsL6DBo2PIJQU7NIKySX0yneLfOsYoVn4gInK2v0qyeE56ExvpqH3Kdnm7We+xP+4CriBU8F++42ui+wl4XDk0rMl7EPW8q6aYCjo2CZvgjH17A+rbnGt4c Y9ZVW+/h Bit4eziZQRQLCdbnuVf+FUEd7yZMVVkKtAOqFuRoRRE7/V/W9mMffKg9I3yShSClnMvuJtlSs+zuZJ2cqO7KumRiicIfVy+TV/L3BsFpwLkrH9ce20aCyuNFa5XP60KZkPkejH7PLd25PuOGClrHR+fCQUNpI+f+6ossB/lbS2VcL8XHAZoGq3n2aE160UeiFhttk0mTwPdTJNUew748AdwsVfYgAFU466reYxTm1bMdTo6qXBxs5B2bnNSDuTBVaL1ECSIc56gWaVHU= 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: List-Subscribe: List-Unsubscribe: On Tue, Jul 01, 2025 at 04:10:19PM -0700, Dave Hansen wrote: > On 7/1/25 02:58, Kirill A. Shutemov wrote: > > Move CR pinning setup behind the EFI initialization. > > I kinda grumble about these one-off solutions. Could we just do this > once and for all and defer CR pinning as long as possible? For instance, > could we do it in a late_initcall()? > > Do we need pinning before userspace comes up? Hm. I operated from an assumption that we want to pin control registers as early as possible to get most benefit from it. I guess we can defer it until later. But I am not sure late_initcall() is the right place. Do we want random driver to twiddle control registers? -- Kiryl Shutsemau / Kirill A. Shutemov