From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] arm64: KVM: use increased VA range if needed
Date: Thu, 26 Feb 2015 15:29:04 +0000 [thread overview]
Message-ID: <1424964547-2118-1-git-send-email-ard.biesheuvel@linaro.org> (raw)
This series addresses the issue where KVM will not be able to initialize
when running on a system whose RAM is located higher in the physical address
space than can be covered with an ID map using VA_BITS of virtual address
space.
Tested on AMD Seattle with 4k pages/VA_BITS==39.
Ard Biesheuvel (3):
ARM, arm64: kvm: get rid of the bounce page
arm64: make ID map shareable with EL2
arm64: KVM: use ID map with increased VA range if required
arch/arm/kernel/vmlinux.lds.S | 12 +++++++++---
arch/arm/kvm/init.S | 11 +++++++++++
arch/arm/kvm/mmu.c | 42 +++++------------------------------------
arch/arm64/kernel/head.S | 22 +++++++++++++++++----
arch/arm64/kernel/vmlinux.lds.S | 20 +++++++++++++-------
arch/arm64/kvm/hyp-init.S | 40 +++++++++++++++++++++++++++++++++++++--
6 files changed, 94 insertions(+), 53 deletions(-)
--
1.8.3.2
next reply other threads:[~2015-02-26 15:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 15:29 Ard Biesheuvel [this message]
2015-02-26 15:29 ` [RFC PATCH 1/3] ARM, arm64: kvm: get rid of the bounce page Ard Biesheuvel
2015-02-26 16:10 ` Marc Zyngier
2015-02-26 17:31 ` Ard Biesheuvel
2015-02-26 18:24 ` Marc Zyngier
2015-02-26 18:41 ` Ard Biesheuvel
2015-02-27 8:19 ` Ard Biesheuvel
2015-02-26 15:29 ` [RFC PATCH 2/3] arm64: make ID map shareable with EL2 Ard Biesheuvel
2015-02-26 15:29 ` [RFC PATCH 3/3] arm64: KVM: use ID map with increased VA range if required Ard Biesheuvel
2015-02-26 16:11 ` Catalin Marinas
2015-02-26 16:29 ` Catalin Marinas
2015-02-26 16:56 ` Ard Biesheuvel
2015-02-26 18:07 ` Catalin Marinas
2015-02-26 18:06 ` Marc Zyngier
2015-02-26 18:17 ` Ard Biesheuvel
2015-02-26 18:51 ` Marc Zyngier
2015-02-26 19:04 ` Ard Biesheuvel
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=1424964547-2118-1-git-send-email-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).