[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] x86/setup: call early_reserve_memory() earlier
- To: Borislav Petkov <bp@xxxxxxxxx>, Mike Rapoport <rppt@xxxxxxxxxx>
- From: Juergen Gross <jgross@xxxxxxxx>
- Date: Thu, 16 Sep 2021 12:31:14 +0200
- Cc: Jan Beulich <jbeulich@xxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, x86@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
- Delivery-date: Thu, 16 Sep 2021 10:31:21 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 16.09.21 12:29, Borislav Petkov wrote:
On Thu, Sep 16, 2021 at 12:09:27PM +0300, Mike Rapoport wrote:
I think the first sentence about reserving memory before memblock
allocations are possible is important and I think we should keep it.
I expanded that comment this way:
/*
* Do some memory reservations *before* memory is added to memblock, so
* memblock allocations won't overwrite it.
*
* After this point, everything still needed from the boot loader or
* firmware or kernel text should be early reserved or marked not RAM
in
* e820. All other memory is free game.
*
* This call needs to happen before e820__memory_setup() which calls
the
* xen_memory_setup() on Xen dom0 which relies on the fact that those
* early reservations have happened already.
*/
Yes, this seems to be an accurate description.
Juergen
Attachment:
OpenPGP_0xB0DE9DD628BF132F.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
|
