From: Bharat Bhushan <bharat.bhus...@freescale.com>

kvm: powerpc: use cache attributes from linux pte
First patch is moving functions/logic in common code so they can be used on 
booke also.
Second and Third patch is actually setting caching attributes (TLB.WIMGE) using 
corresponding Linux pte.

v5-v6
 - First three patches are already applied from this patchset, so sending 
ramining patches
 - return NULL rather than _pte(0) from lookup_linux_pte() and checking for 
NULL in caller
 
v3->v5
 - Fix tlb-reference-flag clearing issue (patch 4/6)
 - There was a patch (4/6 powerpc: move linux pte/hugepte search to more 
generic file)
   in the last series of this patchset which was moving pte/hugepte search 
functions to
   generic file. That patch is no more needed as some other patch is already 
applied to fix that :)

v2->v3
 - now lookup_linux_pte() only have pte search logic and it does not
   set any access flags in pte. There is already a function for setting
   access flag which will be called explicitly where needed.
   On booke we only need to search for pte to get WIMG.

v1->v2
 - Earlier caching attributes (WIMGE) were set based of page is RAM or not
   But now we get these attributes from corresponding Linux PTE.

*** BLURB HERE ***

Bharat Bhushan (3):
  kvm: powerpc: keep only pte search logic in lookup_linux_pte
  kvm: booke: clear host tlb reference flag on guest tlb invalidation
  kvm: powerpc: use caching attributes as per linux pte

 arch/powerpc/include/asm/kvm_host.h |    2 +-
 arch/powerpc/include/asm/pgtable.h  |   24 +++++++++++++++
 arch/powerpc/kvm/book3s_hv_rm_mmu.c |   36 ++++++++---------------
 arch/powerpc/kvm/booke.c            |    2 +-
 arch/powerpc/kvm/e500.h             |    8 +++--
 arch/powerpc/kvm/e500_mmu_host.c    |   54 +++++++++++++++++++---------------
 6 files changed, 73 insertions(+), 53 deletions(-)


--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to