Re: [PATCH v3 1/2] x86/setup: consolidate early memory reservations

2021-03-03 Thread Baoquan He
On 03/02/21 at 05:17pm, Mike Rapoport wrote: > On Tue, Mar 02, 2021 at 09:04:09PM +0800, Baoquan He wrote: ... > > > +static void __init early_reserve_memory(void) > > > +{ > > > + /* > > > + * Reserve the memory occupied by the kernel between _text and > > > + * __end_of_kernel_reserve symbols.

Re: [PATCH v3 1/2] x86/setup: consolidate early memory reservations

2021-03-02 Thread Mike Rapoport
On Tue, Mar 02, 2021 at 09:04:09PM +0800, Baoquan He wrote: > On 03/02/21 at 12:04pm, Mike Rapoport wrote: > > From: Mike Rapoport > > > > The early reservations of memory areas used by the firmware, bootloader, > > kernel text and data are spread over setup_arch(). Moreover, some of them > >

Re: [PATCH v3 1/2] x86/setup: consolidate early memory reservations

2021-03-02 Thread Baoquan He
On 03/02/21 at 12:04pm, Mike Rapoport wrote: > From: Mike Rapoport > > The early reservations of memory areas used by the firmware, bootloader, > kernel text and data are spread over setup_arch(). Moreover, some of them > happen *after* memblock allocations, e.g trim_platform_memory_ranges() and

[PATCH v3 1/2] x86/setup: consolidate early memory reservations

2021-03-02 Thread Mike Rapoport
From: Mike Rapoport The early reservations of memory areas used by the firmware, bootloader, kernel text and data are spread over setup_arch(). Moreover, some of them happen *after* memblock allocations, e.g trim_platform_memory_ranges() and trim_low_memory_range() are called after