| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
Re: [Xen-ia64-devel] Re: [Xen-devel] [PATCH 0/5][IA64][HVM] Windowscrash
>On Tue, Jan 23, 2007 at 08:06:23AM +0000, Keir Fraser wrote:
>> On 23/1/07 2:40 am, "Masaki Kanno" <kanno.masaki@xxxxxxxxxxxxxx> wrote:
>>
>> > In the ia64 machine, there is an INIT switch. By pushing the
>> > INIT switch, an INIT interruption is generated. The INIT
>> > interruption triggers off when the Windows collects the
>> > crashdump. (I attach a screenshot of the Windows crashdump.)
>>
>> Does ia64 Windows generate a dump if you send it an NMI? That would be a
>> more generic mechanism that would allow x86 HVM to share the same domctl or
>> hvm_op. Otherwise we need a send_init hypercall for ia64 and a send_nmi
>> hypercall for x86, or we need a more vague generic name like
>> "trigger_dump_switch" (which actually is rather attractive now I think
>> about
>> it).
>I support the feature too.
>
>I think being able to post an NMI/INIT is a good feature. It allows you
>to test the feature if your bare hardware don't have it.
>
Hi Tristan,
Thanks for your comments.
>Maybe os-init is not the best name.
Maybe os-init is not the best command name as you say. If you have idea
of command name, could you send it?
>Maybe the balance between code in hypervisor (very small) and code in xm
>(larger) is not very good, but difficule to improve !
I examined oneself. I should have checked a target domain (HVM domain or
PV domain) in hypervisor. I will send the patch which moved the check of
target domain into hypervisor. Maybe not difficult to improve.
Best regards,
Kan
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
| |
|
Home