Re: [Patch] Enable "sysrq c" handler for domU coredump

[Akio Takebe <takebe_akio@jp.fujitsu.com>]

Hi, Horms

> Everyone, how about the below?
>> 1. If crash_kexec() is called on dom0, dom0 do hypercall
>>    then xen do kexec/kdump
>> 2. If crash_kexec() is called on domU, domU do hypercall
>>    then xen do panic_domain(), and domU's core is dumped.
>
>I think that is a good idea, because it gives consistent behaviour
>for dom0 and domU, even though the mechanics differ. Though if
>kexec for domU is merged, things may change at that time.
>
>> So I don't need to modify linux code. :-)
>
>:-)
>
>> Or How about "xm dump"?
>> (Probably I use panic_domain() by hypercall.
>> This way can probably dump HVM domain.)
>
>That is also a good idea, though it could be done as well,
>rather than instead of your crash_kexec() -> hypercall idea.
>
>> I think we need to have the way manually to dump domU, or Xen.
>> (Because for the time when domU or Xen don't panic 
>> and spinloop and so on) 
>
>That is a good point, which makes your xm dump idea somewhat
>more attactive than the crash_kexec() -> hypercall idea.
>But I still think they both make sense.
OK, I'll make "xm dump" soon.
Please wait.

Best Regards,

Akio Takebe