[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z_om0KMBqtbq7g0_@gmail.com>
Date: Sat, 12 Apr 2025 10:39:44 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Arnd Bergmann <arnd@...nel.org>, linux-kernel@...r.kernel.org,
x86@...nel.org, Arnd Bergmann <arnd@...db.de>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andy Shevchenko <andy@...nel.org>,
Matthew Wilcox <willy@...radead.org>,
Sean Christopherson <seanjc@...gle.com>,
Davide Ciminaghi <ciminaghi@...dd.com>,
Paolo Bonzini <pbonzini@...hat.com>, kvm@...r.kernel.org,
Mike Rapoport <rppt@...nel.org>
Subject: Re: [PATCH 05/11] x86: remove HIGHMEM64G support
* Dave Hansen <dave.hansen@...el.com> wrote:
> Has anyone run into any problems on 6.15-rc1 with this stuff?
>
> 0xf75fe000 is the mem_map[] entry for the first page >4GB. It
> obviously wasn't allocated, thus the oops. Looks like the memblock
> for the >4GB memory didn't get removed although the pgdats seem
> correct.
>
> I'll dig into it some more. Just wanted to make sure there wasn't a
> fix out there already.
Not that I'm aware of.
> The way I'm triggering this is booting qemu with a 32-bit PAE kernel,
> and "-m 4096" (or more).
That's a new regression indeed.
Thanks,
Ingo
Powered by blists - more mailing lists