From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 73236CA6B; Fri, 13 Feb 2026 17:20:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771003223; cv=none; b=UOCPfbDpxtiN11us45dBkFzp4vNpXSOWC3cZOD/+jc4W0/7Exku5d6usmQyaAJng7HtnuO7qlVPabMHbXZgKQQDyCzCUe459PKQwTChSVd5PtEjTzdYeIg+mb4g3M0g+yXc1XltpXc4489/+Zndl/2gZFEP0lbDcktruxQhFo/U= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771003223; c=relaxed/simple; bh=+LclX38OrI0KgaAdB7NwBZq/cU/VxYfgDrGVgHh3Das=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=he0MmiaC//sQbpC6d0Za1W8rTjMaDRgt5EJm89kG2Z3IZaLr+9BpLzwyt6eQxrPmi8OE0qo/S8zLJfbXh51oDe0ErX54lH3qrFzhbfDiJyk7aQ9bc2+QFrxIhE6xrzDEOqeGTZtvfEEADmpsc6ymzJdkGQs+rmmi/KwI2mvvXHI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=RJ1me+Rn; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="RJ1me+Rn" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 94FD9C19421; Fri, 13 Feb 2026 17:20:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1771003223; bh=+LclX38OrI0KgaAdB7NwBZq/cU/VxYfgDrGVgHh3Das=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=RJ1me+RnKRGLhGoHAPL4YNLROdA/vGro/41iyTWVy2Gdt0KEOho9/SjGiqsbSefqf 1xzDKDFPT5Szk6Fv+ZI9XQD/8usUWYcksgPbPB2OvRPKWvPcma06V4D2aiXS8aNyo3 ZQYxqO/jyZFdFB9Qm/B6+pvxtb9fqWDSP7IHEkGLEM9+EbgmvHhrI1RUWyDbW3uYUX ZZ3FPkrz/y2ZzfNKqHPbnVfcOKuR47daLLJk063OmuAEYpPz2ng8Yi4iYlElrOBkaD YIHiDpB+adsNNxxEn+fEISFIwJalS78sZRd/4cfAQBW8afO+qI8hCnQIXs9G5mVech dp0LmRZQCJfjw== Received: from phl-compute-11.internal (phl-compute-11.internal [10.202.2.51]) by mailfauth.phl.internal (Postfix) with ESMTP id 9E448F4006E; Fri, 13 Feb 2026 12:20:21 -0500 (EST) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-11.internal (MEProxy); Fri, 13 Feb 2026 12:20:21 -0500 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgddvtdekkeefucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepmfhirhihlhcu ufhhuhhtshgvmhgruhcuoehkrghssehkvghrnhgvlhdrohhrgheqnecuggftrfgrthhtvg hrnhepueeijeeiffekheeffffftdekleefleehhfefhfduheejhedvffeluedvudefgfek necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepkhhirh hilhhlodhmvghsmhhtphgruhhthhhpvghrshhonhgrlhhithihqdduieduudeivdeiheeh qddvkeeggeegjedvkedqkhgrsheppehkvghrnhgvlhdrohhrghesshhhuhhtvghmohhvrd hnrghmvgdpnhgspghrtghpthhtohepvdeipdhmohguvgepshhmthhpohhuthdprhgtphht thhopegurghvvgdrhhgrnhhsvghnsehinhhtvghlrdgtohhmpdhrtghpthhtoheprhhpph htsehkvghrnhgvlhdrohhrghdprhgtphhtthhopegrrhgusgeskhgvrhhnvghlrdhorhhg pdhrtghpthhtohepthhglhigsehkvghrnhgvlhdrohhrghdprhgtphhtthhopehmihhngh hosehrvgguhhgrthdrtghomhdprhgtphhtthhopegsphesrghlihgvnhekrdguvgdprhgt phhtthhopegurghvvgdrhhgrnhhsvghnsehlihhnuhigrdhinhhtvghlrdgtohhmpdhrtg hpthhtohepthhhohhmrghsrdhlvghnuggrtghkhiesrghmugdrtghomhdprhgtphhtthho peigkeeisehkvghrnhgvlhdrohhrgh X-ME-Proxy: Feedback-ID: i10464835:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 13 Feb 2026 12:20:19 -0500 (EST) Date: Fri, 13 Feb 2026 17:20:14 +0000 From: Kiryl Shutsemau To: Dave Hansen , Mike Rapoport Cc: Ard Biesheuvel , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , Tom Lendacky , x86@kernel.org, linux-efi@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Moritz Sanft Subject: Re: [PATCH 1/2] efi: Fix reservation of unaccepted memory table Message-ID: References: <20260213154838.46567-1-kas@kernel.org> <20260213154838.46567-2-kas@kernel.org> <6d6dd421-774c-4f29-84d5-3e449240eb93@intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6d6dd421-774c-4f29-84d5-3e449240eb93@intel.com> On Fri, Feb 13, 2026 at 08:46:55AM -0800, Dave Hansen wrote: > On 2/13/26 08:14, Kiryl Shutsemau wrote: > >> The memblock code seems to be able to handle arbitrary alignment just fine. > > Memblock will track it, but, as the comment says, anything smaller than > > page size will not be mapped, but we need the table to be accessible by > > kernel. > > That seems really, really fragile. > > We should first make sure this is intentional memblock behavior and not > a bug before we go add more hacks on top of it. > > Why would you even present a byte-level reservation interface if it is > free to just silently ignore some of the ranges by rounding them off later? +Mike. My guess that multiple memblock_add() calls might add up to the full page size. -- Kiryl Shutsemau / Kirill A. Shutemov