kvm/ppc/e500: h2g_tlb1_rmap: esel 0 is valid
authorScott Wood <scottwood@freescale.com>
Wed, 13 Feb 2013 19:37:48 +0000 (19:37 +0000)
committerAlexander Graf <agraf@suse.de>
Thu, 11 Apr 2013 13:53:34 +0000 (15:53 +0200)
commit6b2ba1a9129bd98b5268a4efb167c95189b3eabf
tree72ac17d7e0226480321e95786dbc285676282f0c
parentc5e6cb051c5f7d56f05bd6a4af22cb300a4ced79
kvm/ppc/e500: h2g_tlb1_rmap: esel 0 is valid

Add one to esel values in h2g_tlb1_rmap, so that "no mapping" can be
distinguished from "esel 0".  Note that we're not saved by the fact
that host esel 0 is reserved for non-KVM use, because KVM host esel
numbering is not the raw host numbering (see to_htlb1_esel).

Signed-off-by: Scott Wood <scottwood@freescale.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
arch/powerpc/kvm/e500_mmu_host.c