RE: [Xen-ia64-devel] [Patch] Guest PAL_INIT support for IPI

["Zhang, Xing Z" <xing.z.zhang@xxxxxxxxx>]

Oh, I forgot restart xend last time.
But this time I get another error info. See attachment

Good good study,day day up ! ^_^
-Wing(zhang xin)
 
OTC,Intel Corporation

-----Original Message-----
From: Akio Takebe [mailto:takebe_akio@xxxxxxxxxxxxxx] 
Sent: 2006年11月7日 14:55
To: Zhang, Xing Z; Masaki Kanno; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Cc: Akio Takebe
Subject: RE: [Xen-ia64-devel] [Patch] Guest PAL_INIT support for IPI

Hi, Wing

Could you try it again after "xend stop; xend start".

Best Regards,

Akio Takebe

>New GFW will release soon, I think it's today.
>I used your merge.patch but failed. Seems some problems in python code.
>Attachment is a picture show the issue 
>
>Good good study,day day up ! ^_^
>-Wing(zhang xin)
> 
>OTC,Intel Corporation
>
>-----Original Message-----
>From: Akio Takebe [mailto:takebe_akio@xxxxxxxxxxxxxx] 
>Sent: 2006年11月7日 13:39
>To: Zhang, Xing Z; Masaki Kanno; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] [Patch] Guest PAL_INIT support for IPI
>
>Hi, Wing
>
>I don't know, but if you give me newer GFW, 
>we'll test "xm os-init" on windows of domVTi.
>
>Best Regards,
>
>Akio Takebe
>
>>I still have a question:
>> How windows OS_INIT handler do? How can I confirm whether PAL_INIT executed
>> successful in windows? ( in Linux , I can see a lot of dump info on screen) 
>>
>>Good good study,day day up ! ^_^
>>-Wing(zhang xin)
>> 
>>OTC,Intel Corporation
>>
>>-----Original Message-----
>>From: Masaki Kanno [mailto:kanno.masaki@xxxxxxxxxxxxxx] 
>>Sent: 2006ト・1ヤツ6ネユ 18:18
>>To: Zhang, Xing Z; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>Subject: Re: [Xen-ia64-devel] [Patch] Guest PAL_INIT support for IPI
>>
>>Hi Zhang,
>>
>>We were looking forward to your patches. 
>>We have a question and a comment.
>>
>>Question:
>>  How can we inject the INIT interrupt into domVTi?
>>  We made xm os-init command, and tested your patch.
>>  But INIT handler of domVTi was not executed, we think.
>>  We attach two files.
>>   - merge.patch : It is a patch that we tested.
>>   - xenctx.log  : It is a cpu-context of domVTi after we test.
>>
>>Comment:
>>  We think that TODO line is unnecessary.
>>
>>@@ -404,7 +419,7 @@ static void deliver_ipi (VCPU *vcpu, uin
>>         break;
>>     case 5:     // INIT
>>         // TODO -- inject guest INIT        <---------- This!
>>-        panic_domain (NULL, "Inject guest INIT!\n");
>>+        vmx_inject_guest_pal_init(vcpu);
>>         break;
>>     case 7:     // ExtINT
>>         vmx_vcpu_pend_interrupt (vcpu, 0);
>>
>>Best regards,
>> Kan and Akio
>>
>>>This patch add guest PAL_INIT support for IPI
>>>
>>> 
>>>
>>>Signed-off-by, Zhang Xin < xing.z.zhang@xxxxxxxxx
>>>
>>> 
>>>
>>>Good good study,day day up ! ^_^
>>>
>>>-Wing(zhang xin)
>>>
>>> 
>>>
>>>OTC,Intel Corporation
>>>
>>> 
>>>
>>>
>>>-------------------------------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

Attachment: xm_os_init2.png
Description: xm_os_init2.png

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel