From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 632223B9DB3; Tue, 15 Sep 2026 14:35:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789482936; cv=none; b=pNII3ibBn/mn2EWNu1YDSFUYhffKHpaE1maDsoOTdmhcViFhXVQfetax9WaubO0LSLL3fcbi23BwilikNyuN35hEP1VLm4mHe24sucuMR2BZP9C9/vqTLlLJhgmy4Y2J+bpSqDt9qf0Mi2/kOF5ww72tvGf8aCRufP+FoB25IVI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789482936; c=relaxed/simple; bh=xC1xzO73V/QVx+SUYTQZLLliucmabiID20h8fopd7zM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=qhZHmxndNmK54ZVOgcMRFJAorUmKZx5B2mOUtDhUt/iziTTltaS+phPesFQpOprYvkdMqbYYVKCwKHrraS49E+BQ2eJTKsS/JDHNK6THL53mfMgQ0XAf9OUJlqKrk6cd8F0qVODj6Mb2wxrIAyB1LU3J8LuY2EcSaH6V0Ps3Cto= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=VtKFlspQ; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="VtKFlspQ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 806681F000FF; Tue, 15 Sep 2026 14:35:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1789482935; bh=HhkTKZqSauRlzDBmuIch4WSDGbcfsJp9na+AzwvnNew=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=VtKFlspQzOv/Zif2Ow84xQkRnLY0nrqHqoynrLyvg5SIxf+bnjB9jvnYZlJFCKoHk Fsvtg3M88EQ9y23RcTgrVdPVCC12nYfwrTuUPtF7T8/em/9zQkHdQ/95dP05TspWKr wlJbsjBRL2Kjst/08D5KbDCRo3s86XhKAa/vOUrCH037W/omFf9HgCtaWZYqYpWYMl uKKz66IuX3ETy+gTxW9l3SEAwkF8wt6lilp3aw3yD1ss5zU4+IsNIrAC1l7/o+T56X Rlmf4Odr5SnNyIpzIyI9wkTJHAURu7kq0z029COy9SPWurwLO8XzjMUfs1HWzJdOGd 394I86ioQiGRQ== Date: Tue, 15 Sep 2026 15:35:33 +0100 From: Harry Yoo To: Breno Leitao Cc: Ard Biesheuvel , Ilias Apalodimas , Miaohe Lin , Naoya Horiguchi , Andrew Morton , "Kiryl Shutsemau (Meta)" , kexec@lists.infradead.org, David Hildenbrand , Lorenzo Stoakes , "Liam R. Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H . Peter Anvin" , Brendan Jackman , Johannes Weiner , Zi Yan , linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, rmikey@meta.com, riel@surriel.com, kernel-team@meta.com Subject: Re: [PATCH v4 2/5] mm/memory-failure: libstub: install the poisoned-memory EFI table Message-ID: References: <20260909-hwpoison-kho-v4-0-359313564495@debian.org> <20260909-hwpoison-kho-v4-2-359313564495@debian.org> <2c9a7bef-3189-4f78-a6cb-61d2f7afd643@app.fastmail.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=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Tue, Sep 15, 2026 at 06:38:47AM -0700, Breno Leitao wrote: > On Tue, Sep 15, 2026 at 02:31:38PM +0100, Harry Yoo wrote: > > On Tue, Sep 15, 2026 at 05:39:44AM -0700, Breno Leitao wrote: > > > > Also, I wonder if some architectures have a scattered set of pfn > > > > ranges so that the span from the start pfn to the end pfn being much > > > > larger than the actual physical memory size. > > > > > > > > If so it might make more sense to have a bitmap for each pfn range. > > > > > > Agreed, having a ->next in linux_efi_poisoned_memory is a good idea that > > > we can lean on depending on whatever problem comes up down the road. > > > > > > Very good point — let's keep this linux_efi_poisoned_memory chain idea in > > > mind for whenever we need to expand it. > > > > You mean 1) keeping the structure as-is for now (and expand later with > > new EFI table version) or 2) adjusting the structure in the future > > revision of this patchset? > > I'd say option (1): keep the structure as it is for now, and only adjust > it once/if we actually decide to implement the hot-add use case. > > That's exactly why I added the "u32 version" field to > struct linux_efi_poisoned_memory, so, it can be expanded later. Ack. > Version 1 (this patchset) covers the common, basic approach. If down the > road someone sees value in extending it to other use cases (such as > hot-plug), we can bump it to v2 and add a ->next field then. > > What do you think? That will work, no strong opinion here. -- Cheers, Harry / Hyeonggon