From: Jan Beulich <jbeulich@suse.com>
To: Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: [PATCH 5/6] xen/x86: there's no highmem anymore in PV mode
Date: Thu, 30 Sep 2021 14:36:56 +0200 [thread overview]
Message-ID: <ba6e0779-18f4-ae64-b216-73205b4eec3c@suse.com> (raw)
In-Reply-To: <022b1a5e-4121-6bae-f07c-4ad5eac12481@suse.com>
Considerations for it are a leftover from when 32-bit was still
supported.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
--- a/arch/x86/xen/setup.c
+++ b/arch/x86/xen/setup.c
@@ -306,10 +306,6 @@ static void __init xen_update_mem_tables
BUG();
}
- /* Update kernel mapping, but not for highmem. */
- if (pfn >= PFN_UP(__pa(high_memory - 1)))
- return;
-
if (HYPERVISOR_update_va_mapping((unsigned long)__va(pfn << PAGE_SHIFT),
mfn_pte(mfn, PAGE_KERNEL), 0)) {
WARN(1, "Failed to update kernel mapping for mfn=%ld pfn=%ld\n",
next prev parent reply other threads:[~2021-09-30 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 12:33 [PATCH 0/6] xen/x86: PV boot speedup Jan Beulich
2021-09-30 12:34 ` [PATCH 1/6] xen/x86: streamline set_pte_mfn() Jan Beulich
2021-09-30 12:35 ` [PATCH 2/6] xen/x86: restore (fix) xen_set_pte_init() behavior Jan Beulich
2021-09-30 12:35 ` [PATCH 3/6] xen/x86: adjust xen_set_fixmap() Jan Beulich
2021-09-30 12:36 ` [PATCH 4/6] xen/x86: adjust handling of the L3 user vsyscall special page table Jan Beulich
2021-09-30 12:36 ` Jan Beulich [this message]
2021-09-30 12:37 ` [PATCH 6/6] xen/x86: restrict PV Dom0 identity mapping Jan Beulich
2021-10-02 0:33 ` [PATCH 0/6] xen/x86: PV boot speedup Boris Ostrovsky
2021-10-27 13:17 ` Boris Ostrovsky
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=ba6e0779-18f4-ae64-b216-73205b4eec3c@suse.com \
--to=jbeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@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