From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Pavin Joseph <me@pavinjoseph.com>,
Steve Wahl <steve.wahl@hpe.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
Linux regressions mailing list <regressions@lists.linux.dev>,
stable@vger.kernel.org, Eric Hagberg <ehagberg@gmail.com>,
Simon Horman <horms@verge.net.au>,
Dave Young <dyoung@redhat.com>, Sarah Brofeldt <srhb@dbc.dk>,
Russ Anderson <rja@hpe.com>,
Dimitri Sivanich <sivanich@hpe.com>,
Hou Wenlong <houwenlong.hwl@antgroup.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Yuntao Wang <ytcoode@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH v4] x86/mm/ident_map: On UV systems, use gbpages only where full GB page should be mapped.
Date: Sat, 30 Mar 2024 22:55:53 -0500 [thread overview]
Message-ID: <871q7r12d2.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <ZgbCfVPvWroCnGE4@gmail.com> (Ingo Molnar's message of "Fri, 29 Mar 2024 14:30:37 +0100")
Ingo Molnar <mingo@kernel.org> writes:
> * Pavin Joseph <me@pavinjoseph.com> wrote:
>
>> On 3/29/24 13:45, Ingo Molnar wrote:
>> > Just to clarify, we have the following 3 upstream (and soon to be upstream) versions:
>> >
>> > v1: pre-d794734c9bbf kernels
>> > v2: d794734c9bbf x86/mm/ident_map: Use gbpages only where full GB page should be mapped.
>> > v3: c567f2948f57 Revert "x86/mm/ident_map: Use gbpages only where full GB page should be mapped."
>> >
>> > Where v1 and v3 ought to be the same in behavior.
>> >
>> > So how does the failure matrix look like on your systems? Is my
>> > understanding accurate:
>
>> Slight correction:
>>
>> regular boot | regular kexec | nogbpages boot | nogbpages kexec boot
>> -----------------|---------------|----------------|------------------
>> v1: OK | OK | OK | FAIL
>> v2: OK | FAIL | OK | FAIL
>
> Thanks!
>
> So the question is now: does anyone have a theory about in what fashion
> the kexec nogbpages bootup differs from the regular nogbpages bootup to
> break on your system?
>
> I'd have expected the described root cause of the firmware not properly
> enumerating all memory areas that need to be mapped to cause trouble on
> regular, non-kexec nogbpages bootups too. What makes the kexec bootup
> special to trigger this crash?
My blind hunch would be something in the first 1MiB being different.
The first 1MiB is where all of the historical stuff is and where
I have seen historical memory maps be less than perfectly accurate.
Changing what is mapped being the difference between success and failure
sounds like some place that is dark and hard to debug a page fault is
being triggered and that in turn becoming a triple fault.
Paving Joseph is there any chance you can provide your memory map?
Perhaps just cat /proc/iomem?
If I have something to go one other than works/doesn't work I can
probably say something intelligent.
Eric
next prev parent reply other threads:[~2024-03-31 3:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 16:06 [PATCH v4] x86/mm/ident_map: On UV systems, use gbpages only where full GB page should be mapped Steve Wahl
2024-03-28 16:10 ` kernel test robot
2024-03-28 16:17 ` Steve Wahl
2024-03-29 7:15 ` Ingo Molnar
2024-03-29 8:01 ` Pavin Joseph
2024-03-29 8:15 ` Ingo Molnar
2024-03-29 8:56 ` Pavin Joseph
2024-03-29 13:30 ` Ingo Molnar
2024-03-31 3:55 ` Eric W. Biederman [this message]
2024-04-01 13:30 ` Pavin Joseph
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=871q7r12d2.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dyoung@redhat.com \
--cc=ehagberg@gmail.com \
--cc=horms@verge.net.au \
--cc=houwenlong.hwl@antgroup.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=me@pavinjoseph.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=rja@hpe.com \
--cc=sivanich@hpe.com \
--cc=srhb@dbc.dk \
--cc=stable@vger.kernel.org \
--cc=steve.wahl@hpe.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=ytcoode@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.