Re: [PATCH v4] x86/mm/ident_map: On UV systems, use gbpages only where full GB page should be mapped.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Pavin Joseph <me@xxxxxxxxxxxxxxx> wrote:

> On 3/29/24 12:45, Ingo Molnar wrote:
> > Does the 'nogbpages' kernel command line option fail on these systems
> > even outside of kexec (ie. regular boot), or only in combination with
> > kexec?
> 
> Original reporter here, using nogbpages allows for normal bootup, but 
> kexec fails with it on my two similar systems.

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:


           regular boot  | regular kexec | nogbpages boot | nogbpages kexec boot
 ------------------------|---------------------------------------------------
 v1:       OK            | OK            | OK             | FAIL
 v2:       OK            | FAIL          | FAIL           | FAIL

?

Thanks,

	Ingo




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux