linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Dave Hansen <dave.hansen@intel.com>, x86-ml <x86@kernel.org>
Subject: Re: Kernel 6.15-rc2 unable to boot on 32bit x86 with PAE
Date: Tue, 22 Apr 2025 17:02:55 +0930	[thread overview]
Message-ID: <ecca749e-9c84-40ef-ae2a-d630a249b764@gmx.com> (raw)
In-Reply-To: <aAc-h1TJV7do7JXa@gmail.com>



在 2025/4/22 16:30, Ingo Molnar 写道:
> 
> * Borislav Petkov <bp@alien8.de> wrote:
> 
>> On Fri, Apr 18, 2025 at 08:31:23PM +0930, Qu Wenruo wrote:
>>> Hi,
>>>
>>> Recently I'm testing a situation where highmem is involved, thus I'm
>>> building the latest 32bit x86 with HIGHMEM and PAE, and run it inside a qemu
>>> VM.
>>
>> Does that fix it:
>>
>> https://git.kernel.org/tip/1e07b9fad022e0e02215150ca1e20912e78e8ec1
>>
>> ?
> 
> That commit caused other problems - the best fix we have right now is:
> 
> 	https://git.kernel.org/tip/83b2d345e1786fdab96fc2b52942eebde125e7cd

Thanks, I'll take a try again.

But considering how rare 32bit + highmem systems are nowadays, I still 
have one questions/concern:

- How to make sure we really got highmems?
   The kernel docs only mention that highmems need temporary mapping,
   and proper kmap/kunmap() handling.

   But I still didn't have a straightforward idea of how to verify,
   without adding manual ftrace events when a highmem page is hit.

   E.g. free only shows 3GB memory even if I enabled highmem + PAE.

   Since HIGHMEM64G is removed, I'd expect to get some values more like
   4G instead?

Thanks,
Qu


> 
> Thanks,
> 
> 	Ingo



  reply	other threads:[~2025-04-22  7:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 11:01 Qu Wenruo
2025-04-18 16:05 ` Borislav Petkov
2025-04-18 22:26   ` Qu Wenruo
2025-04-22  7:00   ` Ingo Molnar
2025-04-22  7:32     ` Qu Wenruo [this message]
2025-04-22  8:35       ` Mike Rapoport

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=ecca749e-9c84-40ef-ae2a-d630a249b764@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@kernel.org \
    --cc=rppt@kernel.org \
    --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