From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Volodymyr Babchuk <volodymyr_babchuk@epam.com>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Henry Wang <Henry.Wang@arm.com>
Subject: Re: [PATCH][4.17] EFI: don't convert memory marked for runtime use to ordinary RAM
Date: Fri, 30 Sep 2022 16:28:20 +0200 [thread overview]
Message-ID: <Yzb9BDGc45OshRZN@MacBook-Air-de-Roger.local> (raw)
In-Reply-To: <cc0fbcb4-5ea3-178c-e691-9acb7cc9a3a7@suse.com>
On Fri, Sep 30, 2022 at 09:50:40AM +0200, Jan Beulich wrote:
> efi_init_memory() in both relevant places is treating EFI_MEMORY_RUNTIME
> higher priority than the type of the range. To avoid accessing memory at
> runtime which was re-used for other purposes, make
> efi_arch_process_memory_map() follow suit. While on x86 in theory the
> same would apply to EfiACPIReclaimMemory, we don't actually "reclaim"
> E820_ACPI memory there and hence that type's handling can be left alone.
What about dom0? Should it be translated to E820_RESERVED so that
dom0 doesn't try to use it either? I guess using E820_RESERVED
could also confuse dom0 about ACPI data placement.
Thanks, Roger.
next prev parent reply other threads:[~2022-09-30 14:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 7:50 [PATCH][4.17] EFI: don't convert memory marked for runtime use to ordinary RAM Jan Beulich
2022-09-30 11:55 ` Bertrand Marquis
2022-09-30 12:47 ` Luca Fancellu
2022-09-30 12:51 ` Bertrand Marquis
2022-10-04 15:58 ` Jan Beulich
2022-10-05 10:44 ` Julien Grall
2022-10-05 11:55 ` Jan Beulich
2022-10-05 18:09 ` Julien Grall
2022-10-06 8:39 ` Jan Beulich
2022-10-06 14:11 ` Jan Beulich
2022-10-08 19:08 ` Julien Grall
2022-10-10 6:20 ` Jan Beulich
2022-10-10 23:58 ` Stefano Stabellini
2022-10-11 7:52 ` Bertrand Marquis
2022-09-30 12:53 ` Andrew Cooper
2022-09-30 13:07 ` Jan Beulich
2022-09-30 13:35 ` Bertrand Marquis
2022-09-30 14:28 ` Roger Pau Monné [this message]
2022-10-04 8:06 ` Jan Beulich
2022-10-04 9:33 ` Roger Pau Monné
2022-10-04 10:23 ` Jan Beulich
2022-10-04 10:38 ` Roger Pau Monné
2022-10-04 10:44 ` Jan Beulich
2022-10-04 10:54 ` Roger Pau Monné
2022-10-04 12:18 ` Jan Beulich
2022-10-04 12:52 ` Roger Pau Monné
2022-10-04 13:10 ` Jan Beulich
2022-10-04 14:01 ` Roger Pau Monné
2022-10-04 14:39 ` Jan Beulich
2022-10-04 15:20 ` Roger Pau Monné
2022-10-04 15:55 ` Jan Beulich
2022-10-04 10:49 ` Andrew Cooper
2022-10-04 11:09 ` 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=Yzb9BDGc45OshRZN@MacBook-Air-de-Roger.local \
--to=roger.pau@citrix.com \
--cc=Henry.Wang@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=volodymyr_babchuk@epam.com \
--cc=wl@xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).