Hello all,
I met a problem of SPE operation in PowerPC e500v2 KVM, could anyone help to check or provide some suggestions? Thank you.
Test platform: P1024RDB (e500v2)
Kernel version: Linux p1024rdb 3.0.51-rt75
Test case description:
Use SPE to handle data that not aligned in guest. When I execute the case, host will report call_trace and guest will be hung.
Test log:
Host:
root@p1024rdb:/media/ram# qemu-system-ppc -enable-kvm -nographic -M ppce500v2 -kernel uImage.ppce500v2-kvm -initrd /media/ram/fsl-image-core-p1024rdb.ext2.gz -append "root=/dev/ram rw console=ttyS0,115200" -serial tcp::4444,server,telnet -dtb /usr/share/qemu/ppce500v2.dtb -m 256 -net nic,macaddr=52:54:00:12:34:66 -net tap,script=qemu-ifup -monitor /dev/null & [1] 2264 Created kernel irqchip root@p1024rdb:/media/ram# test for existing bridge br0 BusyBox v1.19.4 (2013-01-26 00:01:45 CST) multi-call binary.
Usage: brctl COMMAND [BRIDGE [INTERFACE]]
need to create bridge br0
br0: port 1(eth0) entering forwarding state
brctl: bridge br0: File exists
br0: port 1(eth0) entering forwarding state
br0: port 1(eth0) entering forwarding state
brctl: bridge br0: Device or resource busy created bridge br0
bridge name bridge id STP enabled interfaces
br0 8000.00e00c00de00 no eth0
device tap0 entered promiscuous mode
br0: port 2(tap0) entering forwarding state
br0: port 2(tap0) entering forwarding state QEMU waiting for connection on: telnet:0.0.0.0:4444,server
PHY: mdio@ffe24000:02 - Link is Up - 1000/Full
eth0: no IPv6 routers present
tap0: no IPv6 routers present
br0: port 1(eth0) entering forwarding state
br0: port 2(tap0) entering forwarding state
root@p1024rdb:/media/ram# exit_nr 5
------------[ cut here ]------------
kernel BUG at arch/powerpc/kvm/booke.c:1273!
Oops: Exception in kernel mode, sig: 5 [#2] SMP NR_CPUS=8 P1024 RDB Modules linked in:
NIP: c0045bd4 LR: c0045bd4 CTR: c02a84b0
REGS: eeeb7af0 TRAP: 0700 Tainted: G D (3.0.51-rt75)
MSR: 00029200 <EE,ME,CE,DE> CR: 20000024 XER: 20000000 TASK = eef49400[2280] 'qemu-system-ppc' THREAD: eeeb6000 CPU: 0
GPR00: c0045bd4 eeeb7ba0 eef49400 00000010 00021200 ffffffff c02aafec 0000000d
GPR08: c07385b8 c072e58c c076c8e0 009b7000 20000088 10018bcc ebf60910 00000000
GPR16: 00000000 00000000 100bf93c 100f0000 101315c8 100f0000 1011bb28 10131ba8
GPR24: ffffffff ffffffff 10131c88 0ffedf10 0ffee7c0 00000005 eb867000 ebf60910 NIP [c0045bd4] kvmppc_handle_exit+0x5c/0x674 LR [c0045bd4] kvmppc_handle_exit+0x5c/0x674 Call Trace:
[eeeb7ba0] [c0045bd4] kvmppc_handle_exit+0x5c/0x674 (unreliable) [eeeb7bc0] [c0047730] kvmppc_resume_host+0x19c/0x1fc [eeeb7c20] [c00462ec] kvmppc_vcpu_run+0x100/0x178 [eeeb7cc0] [c0042308] kvm_arch_vcpu_ioctl_run+0x50/0x170
[eeeb7ce0] [c003ed5c] kvm_vcpu_ioctl+0x8a8/0x9f8 [eeeb7ea0] [c00f3d04] do_vfs_ioctl+0xa4/0x764 [eeeb7f10] [c00f4404] sys_ioctl+0x40/0x70 [eeeb7f40] [c000f2c4] ret_from_syscall+0x0/0x3c
--- Exception: c01 at 0xff1f8f8
LR = 0xffb3c28
Instruction dump:
7c008146 38000000 2b9d0029 901e0008 38000001 981e000c 409d001c 3c60c065
7fa4eb78 3863239c 4cc63182 484e1cf9 <0fe00000> 3d20c054 57a0103a 39295f04 ---[ end trace 24047243cb4e127b ]---
root@p1024rdb:/media/ram#
Guest:
root@model:~# chmod 777 spe_align_e500v2
root@model:~# ./spe_align_e500v2
[no response]
Any suggestion will be appreciated. Thank you.
Regards,
Guanhua
--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
