search for: reprogram_timer

...+ * This loop will run again and again, until lucky enough wbinvd + * happens not to expire timer and then loop break, usually it would + * occur 10K~60K times, blocking guest 10s~60s. + * + * reprogram timer to avoid dead_like_loop. + */ +static inline void uc_wbinvd_and_timer_adjust(void) +{ + reprogram_timer(0); + wbinvd(); + reprogram_timer(NOW() + MILLISECS(1)); +} + void vmx_vmenter_helper(const struct cpu_user_regs *regs) { struct vcpu *curr = current; @@ -2974,6 +2991,13 @@ void vmx_vmenter_helper(const struct cpu_user_regs *regs) struct hvm_vcpu_asid *p_asid; bool_t need_fl...

CPUIDLE: Avoid remnant LAPIC timer intr while force hpetbroadcast LAPIC will stop during C3, and resume to work after exit from C3. Considering below case: The LAPIC timer was programmed to expire after 1000us, but CPU enter C3 after 100us and exit C3 at 9xxus. 0us: reprogram_timer(1000us) 100us: entry C3, LAPIC timer stop 9xxus: exit C3 due to unexpected event, LAPIC timer continue running 10xxus: reprogram_timer(1000us), fail due to the past expiring time. ......: no timer softirq raised, no change to LAPIC timer. ......: if entry C3 again, HPET will be forced reprogramed...

...0a1075478b434956fbdb1aad6ebd5 call out to arch code to deliver timer interrupts diff -r df0ad1c46f10 -r 686cd624618c xen/arch/ia64/xen/xentime.c --- a/xen/arch/ia64/xen/xentime.c Thu Mar 9 16:03:23 2006 +0100 +++ b/xen/arch/ia64/xen/xentime.c Tue Mar 14 14:56:55 2006 -0600 @@ -258,4 +258,8 @@ int reprogram_timer(s_time_t timeout) return 1; } - +void arch_send_timer_event(struct vcpu *v) +{ + send_guest_virq(v, VIRQ_TIMER); +} + diff -r df0ad1c46f10 -r 686cd624618c xen/arch/x86/time.c --- a/xen/arch/x86/time.c Thu Mar 9 16:03:23 2006 +0100 +++ b/xen/arch/x86/time.c Tue Mar 14 14:56:55 2006 -0600 @@...

This round implements all of the review comments from V2 and all patches are now acked. Unless there are any objections I intend to apply later this morning. Ian.

First off, Apologies for the massive patch series... This series boots a 32-bit dom0 kernel to a command prompt on an ARMv8 (AArch64) model. The kernel is the same one as I am currently using with the 32 bit hypervisor I haven''t yet tried starting a guest or anything super advanced like that ;-). Also there is not real support for 64-bit domains at all, although in one or two places I

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See