[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <780610f6-de4f-625d-e242-97063cea7cc5@suse.com>
Date: Thu, 16 Sep 2021 12:31:14 +0200
From: Juergen Gross <jgross@...e.com>
To: Borislav Petkov <bp@...en8.de>, Mike Rapoport <rppt@...nel.org>
Cc: Jan Beulich <jbeulich@...e.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Marek Marczykowski-Górecki
<marmarek@...isiblethingslab.com>, xen-devel@...ts.xenproject.org,
x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/setup: call early_reserve_memory() earlier
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
Download attachment "OpenPGP_0xB0DE9DD628BF132F.asc" of type "application/pgp-keys" (3092 bytes)
Download attachment "OpenPGP_signature" of type "application/pgp-signature" (496 bytes)
Powered by blists - more mailing lists