From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] arm64: KVM: Implement 48 VA support for KVM EL2 and Stage-2
Date: Fri, 10 Oct 2014 16:09:10 +0100 [thread overview]
Message-ID: <20141010150908.GA7758@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1412936070-18860-2-git-send-email-christoffer.dall@linaro.org>
On Fri, Oct 10, 2014 at 11:14:28AM +0100, Christoffer Dall wrote:
> This patch adds the necessary support for all host kernel PGSIZE and
> VA_SPACE configuration options for both EL2 and the Stage-2 page tables.
>
> However, for 40bit and 42bit PARange systems, the architecture mandates
> that VTCR_EL2.SL0 is maximum 1, resulting in fewer levels of stage-2
> pagge tables than levels of host kernel page tables. At the same time,
> systems with a PARange > 42bit, we limit the IPA range by always setting
> VTCR_EL2.T0SZ to 24.
>
> To solve the situation with different levels of page tables for Stage-2
> translation than the host kernel page tables, we allocate a dummy PGD
> with pointers to our actual inital level Stage-2 page table, in order
> for us to reuse the kernel pgtable manipulation primitives. Reproducing
> all these in KVM does not look pretty and unnecessarily complicates the
> 32-bit side.
>
> Systems with a PARange < 40bits are not yet supported.
>
> [ I have reworked this patch from its original form submitted by
> Jungseok to take the architecture constraints into consideration.
> There were too many changes from the original patch for me to
> preserve the authorship. Thanks to Catalin Marinas for his help in
> figuring out a good solution to this challenge. I have also fixed
> various bugs and missing error code handling from the original
> patch. - Christoffer ]
>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Signed-off-by: Jungseok Lee <jungseoklee85@gmail.com>
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2014-10-10 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 10:14 [PATCH v3 0/3] arm/arm64: KVM: Host 48-bit VA support and IPA limits Christoffer Dall
2014-10-10 10:14 ` [PATCH v3 1/3] arm64: KVM: Implement 48 VA support for KVM EL2 and Stage-2 Christoffer Dall
2014-10-10 15:09 ` Catalin Marinas [this message]
2014-10-11 8:56 ` Marc Zyngier
2014-10-10 10:14 ` [PATCH v3 2/3] arm/arm64: KVM: Ensure memslots are within KVM_PHYS_SIZE Christoffer Dall
2014-10-10 15:09 ` Catalin Marinas
2014-10-11 9:01 ` Marc Zyngier
2014-10-10 10:14 ` [PATCH v3 3/3] arm64: Allow 48-bits VA space without ARM_SMMU Christoffer Dall
2014-10-10 15:10 ` Catalin Marinas
2014-10-10 21:03 ` Christoffer Dall
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=20141010150908.GA7758@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--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).