From: Bharat Bhushan <r65777@freescale.com>
To: <scottwood@freescale.com>, <benh@kernel.crashing.org>,
<agraf@suse.de>, <paulus@samba.org>, <kvm@vger.kernel.org>,
<kvm-ppc@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>
Cc: Bharat Bhushan <bharat.bhushan@freescale.com>
Subject: [PATCH 0/6 v3] kvm: powerpc: use cache attributes from linux pte
Date: Tue, 6 Aug 2013 17:01:08 +0530 [thread overview]
Message-ID: <1375788674-13140-1-git-send-email-Bharat.Bhushan@freescale.com> (raw)
From: Bharat Bhushan <bharat.bhushan@freescale.com>
First patch is a typo fix where book3e define _PAGE_LENDIAN while it should be
defined as _PAGE_ENDIAN. This seems to show that this is never exercised :-)
Second and third patch is to allow guest controlling "G"-Guarded and
"E"-Endian TLB attributes respectively.
Fourth and fifth patch is moving functions/logic in common code
so they can be used on booke also.
Sixth patch is actually setting caching attributes (TLB.WIMGE) using
corresponding Linux pte.
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.
Bharat Bhushan (6):
powerpc: book3e: _PAGE_LENDIAN must be _PAGE_ENDIAN
kvm: powerpc: allow guest control "E" attribute in mas2
kvm: powerpc: allow guest control "G" attribute in mas2
powerpc: move linux pte/hugepte search to more generic file
kvm: powerpc: keep only pte search logic in lookup_linux_pte
kvm: powerpc: use caching attributes as per linux pte
arch/powerpc/include/asm/kvm_host.h | 2 +-
arch/powerpc/include/asm/pgtable-ppc64.h | 36 ------------------
arch/powerpc/include/asm/pgtable.h | 60 ++++++++++++++++++++++++++++++
arch/powerpc/include/asm/pte-book3e.h | 2 +-
arch/powerpc/kvm/book3s_hv_rm_mmu.c | 38 ++++++-------------
arch/powerpc/kvm/booke.c | 2 +-
arch/powerpc/kvm/e500.h | 10 +++--
arch/powerpc/kvm/e500_mmu_host.c | 36 ++++++++++-------
8 files changed, 102 insertions(+), 84 deletions(-)
next reply other threads:[~2013-08-06 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 11:31 Bharat Bhushan [this message]
2013-08-06 11:31 ` [PATCH 1/6 v3] powerpc: book3e: _PAGE_LENDIAN must be _PAGE_ENDIAN Bharat Bhushan
2013-08-06 11:31 ` [PATCH 2/6 v3] kvm: powerpc: allow guest control "E" attribute in mas2 Bharat Bhushan
2013-08-06 11:31 ` [PATCH 3/6 v3] kvm: powerpc: allow guest control "G" " Bharat Bhushan
2013-08-06 11:31 ` [PATCH 4/6 v3] powerpc: move linux pte/hugepte search to more generic file Bharat Bhushan
2013-08-06 11:31 ` [PATCH 5/6 v3] kvm: powerpc: keep only pte search logic in lookup_linux_pte Bharat Bhushan
2013-08-06 11:31 ` [PATCH 6/6 v3] kvm: powerpc: use caching attributes as per linux pte Bharat Bhushan
2013-08-10 1:04 ` Scott Wood
2013-08-12 17:14 ` Bhushan Bharat-R65777
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=1375788674-13140-1-git-send-email-Bharat.Bhushan@freescale.com \
--to=r65777@freescale.com \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=bharat.bhushan@freescale.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
/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