From: Juergen Gross <jgross@suse.com>
To: Borislav Petkov <bp@alien8.de>, Mike Rapoport <rppt@kernel.org>
Cc: "Jan Beulich" <jbeulich@suse.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel@lists.xenproject.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/setup: call early_reserve_memory() earlier
Date: Thu, 16 Sep 2021 12:31:14 +0200 [thread overview]
Message-ID: <780610f6-de4f-625d-e242-97063cea7cc5@suse.com> (raw)
In-Reply-To: <YUMclVZ5uxKV/bRZ@zn.tnic>
[-- Attachment #1.1.1: Type: text/plain, Size: 1007 bytes --]
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 #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3135 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2021-09-16 10:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 9:41 [PATCH] x86/setup: call early_reserve_memory() earlier Juergen Gross
2021-09-14 10:03 ` Jan Beulich
2021-09-14 11:06 ` Juergen Gross
2021-09-15 11:00 ` Borislav Petkov
2021-09-16 9:09 ` Mike Rapoport
2021-09-16 10:29 ` Borislav Petkov
2021-09-16 10:31 ` Juergen Gross [this message]
2021-09-14 10:49 ` Marek Marczykowski-Górecki
2021-09-16 10:50 ` [tip: x86/urgent] x86/setup: Call " tip-bot2 for Juergen Gross
2021-09-19 16:55 ` Mike Galbraith
2021-09-19 17:04 ` Mike Rapoport
2021-09-20 0:56 ` Mike Galbraith
2021-09-20 9:26 ` Mike Rapoport
2021-09-20 9:38 ` Borislav Petkov
2021-09-20 11:25 ` Mike Galbraith
2021-09-20 11:33 ` Juergen Gross
2021-09-19 17:15 ` Borislav Petkov
2021-09-20 6:00 ` Juergen Gross
2021-09-20 9:46 ` Mike Rapoport
2021-09-20 22:48 ` Nathan Chancellor
2021-09-21 3:38 ` Borislav Petkov
2021-09-21 3:59 ` Nathan Chancellor
2021-09-21 7:36 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=780610f6-de4f-625d-e242-97063cea7cc5@suse.com \
--to=jgross@suse.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=mingo@redhat.com \
--cc=rppt@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.