Freescale P5020 cpu will be kvm-pr?
luigi burdo
intermediadc at hotmail.com
Fri Mar 18 00:38:18 AEDT 2016
Hi Scott,
this is my Kernel 4.5 dmesg
dmesg | grep -i MMU
[ 0.000000] MMU: Supported page sizes
[ 0.000000] MMU: Book3E HW tablewalk not supported
[ 0.000000] mmu_features = 0x000a0010
[ 0.000000] MMU: Allocated 2112 bytes of context maps for 255 contexts
dmesg | grep -i e500
[ 0.001787] e500 family performance monitor hardware support registered
dmesg | grep -i hypervisor
[ 0.396726] ePAPR hypervisor byte channel driver
[ 3.240020] Freescale hypervisor management driver
[ 3.240024] fsl-hv: no hypervisor found
my cpu info
processor : 0
cpu : e5500
clock : 1995.000000MHz
revision : 1.2 (pvr 8024 0012)
processor : 1
cpu : e5500
clock : 1995.000000MHz
revision : 1.2 (pvr 8024 0012)
timebase : 24937500
platform : CoreNet Generic
model : varisys,CYRUS5020
i attached my kenrel .config
My qemu-ppc-64 crash, note i have the same crash
qemu: fatal: This KVM version does not support PAPR
NIP 0000000000000000 LR 0000000000000000 CTR 0000000000000000 XER 0000000000000000 CPU#0
MSR 0000000000000000 HID0 0000000000000000 HF 0000000000000000 idx 0
TB 00000000 00000000 DECR 00000000
GPR00 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR04 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR08 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR12 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR16 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR20 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR24 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR28 0000000000000000 0000000000000000 0000000000000000 0000000000000000
CR 00000000 [ - - - - - - - - ] RES 0000000000000000
FPR00 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR04 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR08 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR12 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR16 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR20 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR24 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPR28 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPSCR 0000000000000000
SRR0 0000000000000000 SRR1 0000000000000000 PVR 0000000080240020 VRSAVE 0000000000000000
SPRG0 0000000000000000 SPRG1 0000000000000000 SPRG2 0000000000000000 SPRG3 0000000000000000
SPRG4 0000000000000000 SPRG5 0000000000000000 SPRG6 0000000000000000 SPRG7 0000000000000000
CSRR0 0000000000000000 CSRR1 0000000000000000 MCSRR0 0000000000000000 MCSRR1 0000000000000000
TCR 0000000000000000 TSR 0000000000000000 ESR 0000000000000000 DEAR 0000000000000000
PIR 0000000000000000 DECAR 0000000000000000 IVPR 0000000000000000 EPCR 0000000000000000
MCSR 0000000000000000 SPRG8 0000000000000000 EPR 0000000000000000
MCAR 0000000000000000 PID1 0000000000000000 PID2 0000000000000000 SVR 0000000000000000
MAS0 0000000000000000 MAS1 0000000000000000 MAS2 0000000000000000 MAS3 0000000000000000
MAS4 0000000000000000 MAS6 0000000000000000 MAS7 0000000000000000 PID 0000000000000000
MMUCFG 0000000000000000 TLB0CFG 0000000004110200 TLB1CFG 00000000401cc040
Aborted (core dumped)
i had been try with more kenel configurations but not change the result.
Thanks for your time
Luigi
> From: oss at buserror.net
> To: intermediadc at hotmail.com
> Date: Wed, 16 Mar 2016 22:47:25 -0500
> Subject: Re: Freescale P5020 cpu will be kvm-pr?
> CC: contact at a-eon.com; matthew at a-eon.com; linuxppc-dev at lists.ozlabs.org; chzigotzky at xenosoft.de
>
> On Wed, 2016-03-16 at 07:24 +0100, luigi burdo wrote:
> > hi Scott,
> > the P5020 mmu is signed by the kernel no book3e found
>
> I don't understand this sentence.
>
> > kvm ppc64 crash if run by qemu.
>
> You didn't show that log.
>
> > in the kernel( 4.5 too)all is enabled we had a base .config by freescale/nix
> > where kvm options and book3e where enabled.
>
> You should start with corenet64_smp_defconfig, and enable KVM options plus
> PPC_QEMU_E500.
>
> > my suspect is this can be an generated issue by the host uboot
>
> Host U-Boot has nothing to do with KVM.
>
> > or a missed tdb parameter and not a linux kernel problem.
>
> What is tdb?
>
> -Scott
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-devFailed to load module Failed to
> From: oss at buserror.net
> To: intermediadc at hotmail.com
> Date: Wed, 16 Mar 2016 22:47:25 -0500
> Subject: Re: Freescale P5020 cpu will be kvm-pr?
> CC: contact at a-eon.com; matthew at a-eon.com; linuxppc-dev at lists.ozlabs.org; chzigotzky at xenosoft.de
>
> On Wed, 2016-03-16 at 07:24 +0100, luigi burdo wrote:
> > hi Scott,
> > the P5020 mmu is signed by the kernel no book3e found
>
> I don't understand this sentence.
>
> > kvm ppc64 crash if run by qemu.
>
> You didn't show that log.
>
> > in the kernel( 4.5 too)all is enabled we had a base .config by freescale/nix
> > where kvm options and book3e where enabled.
>
> You should start with corenet64_smp_defconfig, and enable KVM options plus
> PPC_QEMU_E500.
>
> > my suspect is this can be an generated issue by the host uboot
>
> Host U-Boot has nothing to do with KVM.
>
> > or a missed tdb parameter and not a linux kernel problem.
>
> What is tdb?
>
> -Scott
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20160317/eb35a20b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config
Type: application/octet-stream
Size: 118187 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20160317/eb35a20b/attachment-0001.obj>
More information about the Linuxppc-dev
mailing list