From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: <kvm-ppc@vger.kernel.org>, <kvm@vger.kernel.org>
Subject: Re: [PATCH 3/3] KVM: PPC: e500: Implement TLB1-in-TLB0 mapping
Date: Thu, 17 Jan 2013 18:31:07 -0600 [thread overview]
Message-ID: <1358469067.13978.19@snotra> (raw)
In-Reply-To: <1358463041-25922-4-git-send-email-agraf@suse.de> (from agraf@suse.de on Thu Jan 17 16:50:41 2013)
On 01/17/2013 04:50:41 PM, Alexander Graf wrote:
> When a host mapping fault happens in a guest TLB1 entry today, we
> map the translated guest entry into the host's TLB1.
>
> This isn't particularly clever when the guest is mapped by normal 4k
> pages, since these would be a lot better to put into TLB0 instead.
>
> This patch adds the required logic to map 4k TLB1 shadow maps into
> the host's TLB0.
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
> arch/powerpc/kvm/e500.h | 1 +
> arch/powerpc/kvm/e500_mmu_host.c | 58
> +++++++++++++++++++++++++++++--------
> 2 files changed, 46 insertions(+), 13 deletions(-)
>
> diff --git a/arch/powerpc/kvm/e500.h b/arch/powerpc/kvm/e500.h
> index 00f96d8..d32e6a8 100644
> --- a/arch/powerpc/kvm/e500.h
> +++ b/arch/powerpc/kvm/e500.h
> @@ -28,6 +28,7 @@
>
> #define E500_TLB_VALID 1
> #define E500_TLB_BITMAP 2
> +#define E500_TLB_TLB0 (1 << 2)
>
> struct tlbe_ref {
> pfn_t pfn;
> diff --git a/arch/powerpc/kvm/e500_mmu_host.c
> b/arch/powerpc/kvm/e500_mmu_host.c
> index 3bb2154..cbb6cf8 100644
> --- a/arch/powerpc/kvm/e500_mmu_host.c
> +++ b/arch/powerpc/kvm/e500_mmu_host.c
> @@ -198,6 +198,11 @@ void inval_gtlbe_on_host(struct kvmppc_vcpu_e500
> *vcpu_e500, int tlbsel,
> local_irq_restore(flags);
>
> return;
> + } else if (tlbsel == 1 &&
> + vcpu_e500->gtlb_priv[1][esel].ref.flags &
> E500_TLB_TLB0) {
> + /* This is a slow path, so just invalidate everything */
> + kvmppc_e500_tlbil_all(vcpu_e500);
> + vcpu_e500->gtlb_priv[1][esel].ref.flags &=
> ~E500_TLB_TLB0;
> }
What if the guest TLB1 entry is backed by a mix of TLB0 and TLB1
entries on the host? I don't see checks elsewhere that would prevent
this situation.
> @@ -529,9 +556,14 @@ void kvmppc_mmu_map(struct kvm_vcpu *vcpu, u64
> eaddr, gpa_t gpaddr,
> case 1: {
> gfn_t gfn = gpaddr >> PAGE_SHIFT;
>
> - stlbsel = 1;
> sesel = kvmppc_e500_tlb1_map(vcpu_e500, eaddr, gfn,
> gtlbe, &stlbe, esel);
> + if (sesel < 0) {
> + /* TLB0 mapping */
> + sesel = 0;
> + stlbsel = 0;
> + } else
> + stlbsel = 1;
> break;
> }
Maybe push the call to write_tlbe() into the tlb0/1_map functions,
getting rid of the need to pass sesel/stlbsel/stlbe back?
-Scott
prev parent reply other threads:[~2013-01-18 0:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 22:50 [PATCH 0/3] KVM: PPC: e500: Shadow TLB Improvements Alexander Graf
2013-01-17 22:50 ` [PATCH 1/3] KVM: PPC: e500: Call kvmppc_mmu_map for initial mapping Alexander Graf
2013-01-18 0:11 ` Scott Wood
2013-01-18 0:20 ` Alexander Graf
2013-01-18 0:29 ` Alexander Graf
2013-01-18 0:35 ` Scott Wood
2013-01-18 0:47 ` Scott Wood
2013-01-18 0:49 ` Alexander Graf
2013-01-18 1:16 ` Alexander Graf
2013-01-17 22:50 ` [PATCH 2/3] KVM: PPC: E500: Split host and guest MMU parts Alexander Graf
2013-01-17 22:50 ` [PATCH 3/3] KVM: PPC: e500: Implement TLB1-in-TLB0 mapping Alexander Graf
2013-01-18 0:31 ` Scott Wood [this message]
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=1358469067.13978.19@snotra \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.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