From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi <linux-efi@vger.kernel.org>,
norbert.kaminski@3mdeb.com, xen-devel@lists.xenproject.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] efi: discover ESRT table on Xen PV too
Date: Tue, 18 Aug 2020 13:45:18 +0200 [thread overview]
Message-ID: <20200818114518.GA226001@mail-itl> (raw)
In-Reply-To: <CAMj1kXEQ2mpmcNke0K2MZPAAo9wGZ4h3pCmMg9Hm7CPXOCV7fQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
On Mon, Aug 17, 2020 at 10:16:07AM +0200, Ard Biesheuvel wrote:
> > @@ -331,7 +333,8 @@ void __init efi_esrt_init(void)
> >
> > end = esrt_data + size;
> > pr_info("Reserving ESRT space from %pa to %pa.\n", &esrt_data, &end);
> > - if (md.type == EFI_BOOT_SERVICES_DATA)
> > +
> > + if (efi_enabled(EFI_MEMMAP) && md.type == EFI_BOOT_SERVICES_DATA)
> > efi_mem_reserve(esrt_data, esrt_data_size);
> >
>
> This does not look correct to me. Why doesn't the region need to be
> reserved on a Xen boot? The OS may overwrite it otherwise.
In case of Xen, it is Xen responsibility to do that. Otherwise even if dom0
would not use it, Xen could allocate that physical memory to another
guest.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-18 11:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 0:19 [PATCH] efi: discover ESRT table on Xen PV too Marek Marczykowski-Górecki
2020-08-17 8:16 ` Ard Biesheuvel
2020-08-18 11:45 ` Marek Marczykowski-Górecki [this message]
2020-08-17 9:00 ` Roger Pau Monné
2020-08-18 12:01 ` Marek Marczykowski-Górecki
2020-08-18 12:47 ` Roger Pau Monné
2020-08-18 15:00 ` Marek Marczykowski-Górecki
2020-08-18 17:21 ` Roger Pau Monné
2020-08-18 18:40 ` Marek Marczykowski-Górecki
2020-08-19 8:19 ` Roger Pau Monné
2020-08-19 11:33 ` Norbert Kaminski
2020-08-20 9:30 ` Roger Pau Monné
2020-08-20 9:34 ` Marek Marczykowski-Górecki
2020-08-20 10:20 ` Roger Pau Monné
2020-08-20 9:35 ` Ard Biesheuvel
2020-08-19 7:20 ` Jan Beulich
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=20200818114518.GA226001@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=norbert.kaminski@3mdeb.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox