linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Liu Yu <yu.liu@freescale.com>
To: kvm-ppc@vger.kernel.org, linuxppc-dev@ozlabs.org
Cc: scottwood@freescale.com, kumar.gala@freescale.com,
	Liu Yu <yu.liu@freescale.com>,
	tpiepho@freescale.com, hollisb@us.ibm.com
Subject: [PATCH v2] powerpc/fsl-booke: declare tlbcam_index for use in c file
Date: Fri, 19 Dec 2008 10:34:53 +0800	[thread overview]
Message-ID: <1229654093-11398-1-git-send-email-yu.liu@freescale.com> (raw)

KVM on E500 platform currently utilize TLB1 entries without bothering host,
that is using unused TLB1 entries.

So, KVM needs to read tlbcam_index to know exactly
which TLB1 entry is unused by host.

Signed-off-by: Liu Yu <yu.liu@freescale.com>
---
[v2]
Remove num_tlbcam_entries declare and read from SPRN_TLB1CFG in KVM instead.

 arch/powerpc/include/asm/mmu-fsl-booke.h |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/arch/powerpc/include/asm/mmu-fsl-booke.h b/arch/powerpc/include/asm/mmu-fsl-booke.h
index 925d93c..c86af6c 100644
--- a/arch/powerpc/include/asm/mmu-fsl-booke.h
+++ b/arch/powerpc/include/asm/mmu-fsl-booke.h
@@ -73,6 +73,8 @@
 
 #ifndef __ASSEMBLY__
 
+extern unsigned int tlbcam_index;
+
 typedef struct {
 	unsigned long id;
 	unsigned long vdso_base;
-- 
1.5.4

             reply	other threads:[~2008-12-19  2:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19  2:34 Liu Yu [this message]
2009-01-04  6:57 ` [PATCH v2] powerpc/fsl-booke: declare tlbcam_index for use in c file Liu Yu
2009-01-05 16:26   ` Kumar Gala
2009-01-05 16:52     ` Hollis Blanchard
2009-01-06  4:55       ` [PATCH v2] powerpc/fsl-booke: declare tlbcam_index for use inc file Liu Yu
2009-01-07 15:09 ` [PATCH v2] powerpc/fsl-booke: declare tlbcam_index for use in c file Kumar Gala

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=1229654093-11398-1-git-send-email-yu.liu@freescale.com \
    --to=yu.liu@freescale.com \
    --cc=hollisb@us.ibm.com \
    --cc=kumar.gala@freescale.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=tpiepho@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;
as well as URLs for NNTP newsgroup(s).