[PATCH] fsl-booke: declare tlbcam_index and num_tlbcam_entries for use in c file

[PATCH] fsl-booke: declare tlbcam_index and num_tlbcam_entries for use in c file

[Liu Yu]

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

So, KVM needs to read tlbcam_index and num_tlbcam_entries to know exactly
which TLB1 entry is unused.

Signed-off-by: Liu Yu <yu.liu@freescale.com>
---
 arch/powerpc/include/asm/mmu-fsl-booke.h |    3 +++
 1 files changed, 3 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..049ad8a 100644
--- a/arch/powerpc/include/asm/mmu-fsl-booke.h
+++ b/arch/powerpc/include/asm/mmu-fsl-booke.h
@@ -73,6 +73,9 @@
 
 #ifndef __ASSEMBLY__
 
+extern unsigned int tlbcam_index;
+extern unsigned int num_tlbcam_entries;
+
 typedef struct {
 	unsigned long id;
 	unsigned long vdso_base;
-- 
1.5.4

Re: [PATCH] fsl-booke: declare tlbcam_index and num_tlbcam_entries for use in c file

[Trent Piepho]

On Wed, 10 Dec 2008, Liu Yu wrote:
> KVM on E500 platform currently utilize TLB1 entries without bothering host,
> that is using unused TLB1 entries.
>
> So, KVM needs to read tlbcam_index and num_tlbcam_entries to know exactly
> which TLB1 entry is unused.

Do you need really need num_tlbcam_entries?  It's completely unused and
I've already sent out a patch to remove it.  If you want to know how
big TLB1 is, just read it from SPRN_TLB1CFG.

RE: [PATCH] fsl-booke: declare tlbcam_index and num_tlbcam_entries for use in c file

[Liu Yu]

> -----Original Message-----
> From: Piepho Trent-B16872=20
> Sent: Wednesday, December 10, 2008 10:04 PM
> To: Liu Yu-B13201
> Cc: linuxppc-dev@ozlabs.org; kvm-ppc@vger.kernel.org; Wood=20
> Scott-B07421; Gala Kumar-B11780
> Subject: Re: [PATCH] fsl-booke: declare tlbcam_index and=20
> num_tlbcam_entries for use in c file
>=20
> On Wed, 10 Dec 2008, Liu Yu wrote:
> > KVM on E500 platform currently utilize TLB1 entries without=20
> bothering host,
> > that is using unused TLB1 entries.
> >
> > So, KVM needs to read tlbcam_index and num_tlbcam_entries=20
> to know exactly
> > which TLB1 entry is unused.
>=20
> Do you need really need num_tlbcam_entries?  It's completely=20
> unused and
> I've already sent out a patch to remove it.  If you want to know how
> big TLB1 is, just read it from SPRN_TLB1CFG.
>=20

Ah, I missed your patch.
Certainly I can use SPRN_TLB1CFG.
I thought if kernel provide a way to get it, then I would rather get it
from kernel than from hardware.