From: Jian J Wang <jian.j.wang@intel.com>
To: edk2-devel@lists.01.org
Subject: [PATCH v6 0/2] Fix multiple entries of RT_CODE in memory map
Date: Thu, 16 Nov 2017 15:26:58 +0800 [thread overview]
Message-ID: <20171116072700.11456-1-jian.j.wang@intel.com> (raw)
> v6
> a. Add workaround in core to filter out all paging related capabilities.
> This is to fix boot issue in Fedora 26 and Windows Server 2016.
> b. Add code to check if EFI_MEMORY_XP should be added for GCD memory map
More than one entry of RT_CODE memory might cause boot problem for some
old OSs. This patch will fix this issue to keep OS compatibility as much
as possible.
Jian J Wang (2):
MdeModulePkg/DxeCore: Filter out all paging capabilities
UefiCpuPkg/CpuDxe: Fix multiple entries of RT_CODE in memory map
MdeModulePkg/Core/Dxe/Mem/Page.c | 17 ++++++++
UefiCpuPkg/CpuDxe/CpuPageTable.c | 94 +++++++++++++++++++++++++++++++---------
2 files changed, 90 insertions(+), 21 deletions(-)
--
2.14.1.windows.1
next reply other threads:[~2017-11-16 16:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 7:26 Jian J Wang [this message]
2017-11-16 7:26 ` [PATCH v6 1/2] MdeModulePkg/DxeCore: Filter out all paging capabilities Jian J Wang
2017-11-16 9:24 ` Ard Biesheuvel
2017-11-16 9:28 ` Zeng, Star
2017-11-16 9:29 ` Ard Biesheuvel
2017-11-16 9:48 ` Zeng, Star
2017-11-16 16:06 ` Ard Biesheuvel
2017-11-17 1:37 ` Yao, Jiewen
2017-11-17 2:48 ` Wang, Jian J
2017-11-22 7:30 ` Zeng, Star
2017-11-20 20:23 ` Laszlo Ersek
2017-11-21 6:29 ` Wang, Jian J
2017-11-16 7:27 ` [PATCH 2/2] UefiCpuPkg/CpuDxe: Fix multiple entries of RT_CODE in memory map Jian J Wang
2017-11-20 20:31 ` Laszlo Ersek
2017-11-21 6:51 ` Wang, Jian J
2017-11-22 7:54 ` Zeng, Star
2017-11-20 21:08 ` [PATCH v6 0/2] " Laszlo Ersek
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-list 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=20171116072700.11456-1-jian.j.wang@intel.com \
--to=devel@edk2.groups.io \
/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