| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
RE: [Xen-ia64-devel] Catch up for PV_on_HVM (cont..)
Understand now,
Thank you for your detailed explanation.
-Anthony
>-----Original Message-----
>From: micky@xxxxxxxxxxxxxxxxxxxxxxxxxxx
>[mailto:micky@xxxxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
>Doi.Tsunehisa@xxxxxxxxxxxxxx
>Sent: 2006?8?29? 14:12
>To: Xu, Anthony
>Cc: DOI Tsunehisa; xen-ia64-devel
>Subject: Re: [Xen-ia64-devel] Catch up for PV_on_HVM (cont..)
>
> Hi Anthony,
>
> Thank you for your comment.
>
>You (anthony.xu) said:
>> I noticed that you use do_yield instead of do_block in xen-event.patch.
>>
>> I think do_yield will incur some unnecessary schedule before it can resume
>> to Guest.
>
> Is this comment about vmx_send_assist_req() ?
>
> So, it sets _VCPUF_blocked_in_xen flags before the code to use
>do_yield. Thus, the VTi domain will be blocked until clear flags
>via new xen-evtchn notification, I think.
>
>** cf. evtchn_send() in xen/common/event_channel.c
>--
>土肥でした．．．
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
| |
|
Home