public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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 2/6] KVM: PPC: E500: Explicitly mark shadow maps invalid
Date: Thu, 17 Jan 2013 21:05:33 -0600	[thread overview]
Message-ID: <1358478333.13978.29@snotra> (raw)
In-Reply-To: <1358476497-15215-3-git-send-email-agraf@suse.de> (from agraf@suse.de on Thu Jan 17 20:34:53 2013)

On 01/17/2013 08:34:53 PM, Alexander Graf wrote:
> When we invalidate shadow TLB maps on the host, we don't mark them
> as not valid. But we should.
> 
> Fix this by removing the E500_TLB_VALID from their flags when
> invalidating.
> 
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
>  arch/powerpc/kvm/e500_tlb.c |   13 ++++++++++---
>  1 files changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/powerpc/kvm/e500_tlb.c b/arch/powerpc/kvm/e500_tlb.c
> index d38ad63..8efb2ac 100644
> --- a/arch/powerpc/kvm/e500_tlb.c
> +++ b/arch/powerpc/kvm/e500_tlb.c
> @@ -204,9 +204,13 @@ static void inval_gtlbe_on_host(struct  
> kvmppc_vcpu_e500 *vcpu_e500,
>  {
>  	struct kvm_book3e_206_tlb_entry *gtlbe =
>  		get_entry(vcpu_e500, tlbsel, esel);
> +	struct tlbe_ref *ref = &vcpu_e500->gtlb_priv[tlbsel][esel].ref;
> 
> -	if (tlbsel == 1 &&
> -	    vcpu_e500->gtlb_priv[1][esel].ref.flags & E500_TLB_BITMAP) {
> +	/* Don't bother with unmapped entries */
> +	if (!(ref->flags & E500_TLB_VALID))
> +		return;
> +
> +	if (tlbsel == 1 && ref->flags & E500_TLB_BITMAP) {
>  		u64 tmp = vcpu_e500->g2h_tlb1_map[esel];
>  		int hw_tlb_indx;
>  		unsigned long flags;
> @@ -224,7 +228,7 @@ static void inval_gtlbe_on_host(struct  
> kvmppc_vcpu_e500 *vcpu_e500,
>  		}
>  		mb();
>  		vcpu_e500->g2h_tlb1_map[esel] = 0;
> -		vcpu_e500->gtlb_priv[1][esel].ref.flags &=  
> ~E500_TLB_BITMAP;
> +		ref->flags &= ~(E500_TLB_BITMAP | E500_TLB_VALID);
>  		local_irq_restore(flags);
> 
>  		return;
> @@ -232,6 +236,9 @@ static void inval_gtlbe_on_host(struct  
> kvmppc_vcpu_e500 *vcpu_e500,
> 
>  	/* Guest tlbe is backed by at most one host tlbe per shadow  
> pid. */
>  	kvmppc_e500_tlbil_one(vcpu_e500, gtlbe);
> +
> +	/* Mark the TLB as not backed by the host anymore */
> +	ref->flags &= ~E500_TLB_VALID;
>  }

Invalidation paths that call kvmppc_e500_tlbil_all(), such as MMUCSR0  
and tlbivax, need a call to clear_tlb_refs() in order to get the valid  
bits cleared.

In looking this up, I also saw that tlbilxlpid (T=0) seems to be  
broken; it compares PID/TID as if it were T=1.  Don't be fooled by the  
"lpid" in the name; it's still relevant (and different from T=1) in the  
absence of E.HV, and should be treated as "tlbilx all".  Once  
implemented, that will also presumably use kvmppc_e500_tlbil_all().

-Scott

  reply	other threads:[~2013-01-18  3:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18  2:34 [PATCH v2 0/6] KVM: PPC: e500: Shadow TLB Improvements v2 Alexander Graf
2013-01-18  2:34 ` [PATCH 1/6] KVM: PPC: E500: Move write_stlbe higher Alexander Graf
2013-01-18  2:34 ` [PATCH 2/6] KVM: PPC: E500: Explicitly mark shadow maps invalid Alexander Graf
2013-01-18  3:05   ` Scott Wood [this message]
2013-01-18 14:08     ` Alexander Graf
2013-01-18 19:03       ` Scott Wood
2013-01-18  2:34 ` [PATCH 3/6] KVM: PPC: E500: Propagate errors when shadow mapping Alexander Graf
2013-01-18  2:34 ` [PATCH 4/6] KVM: PPC: e500: Call kvmppc_mmu_map for initial mapping Alexander Graf
2013-01-18  2:34 ` [PATCH 5/6] KVM: PPC: E500: Split host and guest MMU parts Alexander Graf
2013-01-18  2:34 ` [PATCH 6/6] KVM: PPC: e500: Implement TLB1-in-TLB0 mapping Alexander Graf

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=1358478333.13978.29@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