From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xenproject.org
Subject: [PATCH 0/5] xen: fix dom0 PV boot on some AMD machines
Date: Wed, 7 Aug 2024 12:33:31 +0200 [thread overview]
Message-ID: <20240807103338.22007-1-jgross@suse.com> (raw)
There have been reports of failed boots with Xen due to an overlap of
the kernel's memory with ACPI NVS reported in the E820 map of the host.
This series fixes this issue by moving the NVS area in dom0 to some
higher address.
Juergen Gross (5):
xen: use correct end address of kernel for conflict checking
xen: introduce generic helper checking for memory map conflicts
xen: move checks for e820 conflicts further up
xen: move max_pfn in xen_memory_setup() out of function scope
xen: tolerate ACPI NVS memory overlapping with Xen allocated memory
arch/x86/xen/mmu_pv.c | 5 +-
arch/x86/xen/setup.c | 242 +++++++++++++++++++++++++++++++++--------
arch/x86/xen/xen-ops.h | 3 +-
3 files changed, 201 insertions(+), 49 deletions(-)
--
2.43.0
next reply other threads:[~2024-08-07 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 10:33 Juergen Gross [this message]
2024-08-07 10:33 ` [PATCH 1/5] xen: use correct end address of kernel for conflict checking Juergen Gross
2024-08-07 10:33 ` [PATCH 2/5] xen: introduce generic helper checking for memory map conflicts Juergen Gross
2024-08-07 10:33 ` [PATCH 3/5] xen: move checks for e820 conflicts further up Juergen Gross
2024-08-07 10:33 ` [PATCH 4/5] xen: move max_pfn in xen_memory_setup() out of function scope Juergen Gross
2024-08-07 10:33 ` [PATCH 5/5] xen: tolerate ACPI NVS memory overlapping with Xen allocated memory Juergen Gross
2024-08-07 10:37 ` [PATCH 0/5] xen: fix dom0 PV boot on some AMD machines Jürgen Groß
2024-08-07 10:41 Juergen Gross
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=20240807103338.22007-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®