Re: [PATCH 2/2] x86/mm/KASLR: Adjust the vmemmap size according to paging mode

From: Baoquan He
Date: Thu Aug 30 2018 - 11:25:20 EST

Next message: David Laight: "RE: [PATCH] perf event-parse: Use fixed size string for comms"
Previous message: Douglas Anderson: "[RFT PATCH 1/2] pinctrl: ssbi-gpio: Fix pm8xxx_pin_config_get() to be compliant"
In reply to: Baoquan He: "Re: [PATCH 2/2] x86/mm/KASLR: Adjust the vmemmap size according to paging mode"
Next in thread: Kirill A. Shutemov: "Re: [PATCH 1/2] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Kirill,

I made a new version according to your suggestion, just a little
different, I didn't make 1TB as default, just calculate with the actual
size, then align up to 1TB boundary. Just found kcore is printing more
entries than before, I thought it's caused by my code, later got it was
touchde by other people.

Any comment about this? I can change accordingly.

Next message: David Laight: "RE: [PATCH] perf event-parse: Use fixed size string for comms"
Previous message: Douglas Anderson: "[RFT PATCH 1/2] pinctrl: ssbi-gpio: Fix pm8xxx_pin_config_get() to be compliant"
In reply to: Baoquan He: "Re: [PATCH 2/2] x86/mm/KASLR: Adjust the vmemmap size according to paging mode"
Next in thread: Kirill A. Shutemov: "Re: [PATCH 1/2] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]