|
|
|
|
|
|
|
|
|
|
xen-ia64-devel
RE: [Xen-ia64-devel] Catch up for PV_on_HVM (cont..)
Hi Tsunehisa,
Sorry for very late response,
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.
And if there are only VTI-domain and IDLE-domain running on one LP,
VTI-domain calling do_yield will not be scheduled out,
Then pal_halt_light will not be called on this LP,
On HT(hyperthread) platform, this make another LP on the same core scheduled
less.
Thanks,
Anthony
>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of DOI
>Tsunehisa
>Sent: 2006年8月22日 15:46
>To: xen-ia64-devel
>Subject: [Xen-ia64-devel] Catch up for PV_on_HVM (cont..)
>
>Hi all,
>
> I will post patches for catching up the remain features for PV-on-HVM.
>
>> * need to catchup for IPF
>> + 02.ioemu_xen_evtchns.diff: applied (cs:10974-10976) *not yet*
>> - Flip the device model over to using the new Xen event channels
>> + 04.hvm_inter.diff: applied (cs:11057)
>> - Add support for sending event channel interrupts to HVM guests.
>> + 10.hvm_op_hypercall.diff: applied (cs:11079)
>> - Add stubs to Linux for the new hvm_op hypercall.
>> + 12.add_maddr_h.diff: applied (cs:11081) *not yet*
>> - Split useful bits of page.h into new header maddr.h.
>> + **hvm_op fixup**: applied (cs:11070)
>> - HVMOP_get_param return parameter value within the provided
>> parameter struct
>
> I had posted several patches for these features, a few days ago.
>
>> * catch up `hvm_op fixup'
>> - This patch modifies HYPERVISOR_hvm_op().
>> * catch up `hvm_inter'
>> - This patch adds support for sending event channel interrupts
>> to VT-i guests.
>> * catch up `hvm_op_hypercall'
>> - This patch includes HYPERVISOR_hvm_op() stabs for linux.
>
> This patch includes:
>
> * catch up `split maddr.h'
> - Split page.h into maddr.h
> - This patch is like Alex's patch, but it includes preparation
> for PV-on-HVM.
> * catch up `new Xen event channles'
> - DM over to using the new Xen event channel for IPF
> - Modify xc_ia64_hvm_build for using the new Xen event channel
> - We can't use wait_on_xen_event_channel() macro as x86 code.
> Because IPF code is different with x86 code about MMIO
> emulation. In x86 code, it waits for MMIO completion
> at scheduler tail code. The purpose of the code is enabling
> interupt handling during MMIO intercepts. But, in IPF code,
> it's different.
> - We will want to modify IPF code like x86 code in the future.
>
>Thanks,
>- Tsunehisa Doi
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
|
|