From: Em Sharnoff <sharnoff@neon.tech>
To: Dave Hansen <dave.hansen@intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org
Cc: Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
Oleg Vasilev <oleg@neon.tech>,
Arthur Petukhovsky <arthur@neon.tech>,
Stefan Radig <stefan@neon.tech>, Misha Sakhnov <misha@neon.tech>
Subject: Re: [PATCH v3 1/2] x86/mm: Handle alloc failure in phys_*_init()
Date: Fri, 13 Jun 2025 21:17:33 +0100 [thread overview]
Message-ID: <cce191c5-1467-44a5-8f8f-56dde0e05fb2@neon.tech> (raw)
In-Reply-To: <586a10c2-fc65-4b39-add6-c383bbf46078@intel.com>
On 6/11/25 20:36, Dave Hansen wrote:
> On 6/11/25 12:26, Em Sharnoff wrote:
> > 2. Change the phys_*_init() functions to return int, and directly update
> > max_pfn_mapped from within them. They already call update_page_count(),
> > maybe this is similar?
>
> That seems like the most straightforward. Each time they update a
> mapping, they call a helper which bumps up 'max_pfn_mapped'.
Update on this -- turns out I was wrong again. 'paddr_last' is also used to
update 'pfn_mapped', which is more complex. Hopefully still within reason.
I've posted a new patch set, patch 1/4 adopts the "call a helper" route.
Design-wise, it's less clean than I'd like, but let me know what you think.
https://lore.kernel.org/all/7d0d307d-71eb-4913-8023-bccc7a8a4a3d@neon.tech/
Em
next prev parent reply other threads:[~2025-06-13 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 10:15 [PATCH v3 0/2] x86/mm: Improve alloc handling of phys_*_init() Em Sharnoff
2025-06-10 10:16 ` [PATCH v3 1/2] x86/mm: Handle alloc failure in phys_*_init() Em Sharnoff
2025-06-10 14:55 ` Dave Hansen
2025-06-11 8:38 ` Em Sharnoff
2025-06-11 14:16 ` Dave Hansen
2025-06-11 19:26 ` Em Sharnoff
2025-06-11 19:36 ` Dave Hansen
2025-06-13 20:17 ` Em Sharnoff [this message]
2025-06-11 22:56 ` H. Peter Anvin
2025-06-10 15:07 ` Dave Hansen
2025-06-11 8:39 ` Em Sharnoff
2025-06-10 10:17 ` [PATCH v3 2/2] x86/mm: Use GFP_KERNEL for alloc_low_pages() after boot Em Sharnoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cce191c5-1467-44a5-8f8f-56dde0e05fb2@neon.tech \
--to=sharnoff@neon.tech \
--cc=arthur@neon.tech \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=misha@neon.tech \
--cc=oleg@neon.tech \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=stefan@neon.tech \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox