| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
Re: [Xen-ia64-devel] pickled code
Hi Jes,
When I created a domU, Xen does the panic with your patch.
Because _domain of page_info structure was changed to u64,
type_info of page_info structure is not 8 bytes alignment.
Best regards,
Kan
Kernel command line: root=/dev/hda1 ro nomca nosmp xencons=tty0 console=tty0 3
PID hash table entries: 2048 (order: 11, 65536 bytes)
lookup_domain_mpa: d 0xf000000007de0080 id 1 current 0xf000000007db8000 id 0
(XEN) lookup_domain_mpa: bad mpa 0xffffc019064 (=> 0x20000000)
(XEN) Warning: UC to WB for mpaddr=ffffc019064
008226018, isr=0x00000a0600000000
(XEN) Unaligned Reference.
(XEN) d 0xf000000004290080 domid 0
(XEN) vcpu 0xf000000004268000 vcpu 0
(XEN)
(XEN) CPU 0
(XEN) psr : 0000121008226018 ifs : 8000000000000994 ip : [<f000000004067191>]
(XEN) ip is at get_page_type+0xf1/0x300
(XEN) unat: 0000000000000000 pfs : 0000000000000ea3 rsc : 0000000000000003
(XEN) rnat: 0000000000000000 bsps: 0000000000000000 pr : 000000000002aa69
(XEN) ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c0270033f
(XEN) csd : 0000000000000000 ssd : 0000000000000000
(XEN) b0 : f000000004029e30 b6 : f0000000040290a0 b7 : a000000100068510
(XEN) f6 : 0ffff8000000000000000 f7 : 1003e6db6db6db6db6db7
(XEN) f8 : 1003e000000000002085a f9 : 1003e0000000000000000
(XEN) f10 : 100079cd99999967f8c00 f11 : 1003e0000000000000139
(XEN) r1 : f0000000043168d0 r2 : e00000001fb5fd90 r3 : e00000001fb5fd91
(XEN) r8 : 0000000000000001 r9 : 0000000000000000 r10 : 0000000000000000
(XEN) r11 : 00000000000009e9 r12 : f00000000426f920 r13 : f000000004268000
(XEN) r14 : ffffffffe0000001 r15 : 0000000007de0080 r16 : 0000000000000000
(XEN) r17 : 07de008080000002 r18 : 0000000007de0080 r19 : 000000001fffffff
(XEN) r20 : f00000000426f928 r21 : ffffffff80000000 r22 : 0000000000000000
(XEN) r23 : 0000000000000000 r24 : f00000000426fe20 r25 : f00000000426fe28
(XEN) r26 : 0000000000000000 r27 : 0000000000000000 r28 : 0000000000000000
(XEN) r29 : 0000000000000001 r30 : 0000000000000000 r31 : f000000007de3828
(XEN)
(XEN) Call Trace:
(XEN) [<f000000004098140>] show_stack+0x80/0xa0
(XEN) sp=f00000000426f550 bsp=f0000000042690c8
(XEN) [<f00000000406c300>] ia64_fault+0x280/0x670
(XEN) sp=f00000000426f720 bsp=f000000004269090
(XEN) [<f000000004095100>] ia64_leave_kernel+0x0/0x310
(XEN) sp=f00000000426f720 bsp=f000000004269090
(XEN) [<f000000004067190>] get_page_type+0xf0/0x300
(XEN) sp=f00000000426f920 bsp=f000000004268fe8
(XEN) [<f000000004029e30>] do_grant_table_op+0x1090/0x18d0
(XEN) sp=f00000000426f920 bsp=f000000004268f00
(XEN) [<f00000000405d0e0>] ia64_hypercall+0x4f0/0xe00
(XEN) sp=f00000000426f940 bsp=f000000004268ea0
(XEN) [<f00000000406c840>] ia64_handle_break+0x150/0x2e0
(XEN) sp=f00000000426fdf0 bsp=f000000004268e68
(XEN) [<f000000004095100>] ia64_leave_kernel+0x0/0x310
(XEN) sp=f00000000426fe00 bsp=f000000004268e68
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Fault in Xen.
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
>Hi,
>
>I found another interesting issue in the code - the way the 'pickle'
>functions work just cannot be right. There is no way one should ever
>try and truncate the output of __pa() to u32 or expect to be able to
>run __va() on a u32 and obtain any level of usable output.
>
>I have to admit I have zero clue what the pickle code is trying to
>achieve, but I am at least fairly confident that something needs to
>be done in this space :(
>
>Cheers,
>Jes
>
>
>-------------------------------text/plain-------------------------------
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
| |
|
Home