Hi, Alex, Horms
Sorry for my late responce.
>> What do you think about it?
>
> The panic does seem a bit much, but shouldn't we return rather than
>continue on with a NULL_VECTOR? Thanks,
Yes, I also thik so.
I'll post the new patch.
I'm yet debugging kexec/kdump on HVM.
I have a question, could you give me advice, Horms?
kexec-tool set the new start address to jump there through
relocate_new_kernel.
Which function do the new start address point?
23 GLOBAL_ENTRY(relocate_new_kernel)
24 .prologue
25 alloc r31=ar.pfs,4,0,0,0
26 .body
27 .reloc_entry:
28 {
[snip...
60 //physical mode code begin
61 mov b6=in1 <<<<<<<<<< this(in1) address
62 dep r28=0,in2,61,3 //to physical address
[snip...]
177 .end_loop:
178 sync.i // for fc.i
179 ;;
180 srlz.i
181 ;;
182 srlz.d
183 ;;
184 br.call.sptk.many b0=b6;;
BTW, xenitp is very useful.
Thanks, Tristan.
Best Regards,
Akio Takebe
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|