search for: vcpu_kick

...t_bool(v->mce_pending) && + ((d->is_hvm) || + guest_has_trap_callback(d, v->vcpu_id, TRAP_machine_check)) ) { - mce_printk(MCE_VERBOSE, "MCE: inject vMCE to HVM DOM %d\n", - d->domain_id); - vcpu_kick(d->vcpu[0]); + mce_printk(MCE_VERBOSE, "MCE: inject vMCE to dom%d vcpu%d\n", + d->domain_id, v->vcpu_id); + vcpu_kick(v); } else { - mce_printk(MCE_VERBOSE, "MCE: inject vMCE to PV DOM%d\n&quot...

In x64 SMP Vista HVM guest (vcpus=2 in the configuration file), the wall clock time is 50% slower than that in the real world. The attached patch fixes the issue. -- Dexuan Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

From: Yang Zhang <yang.z.zhang@Intel.com> The follwoing patches are adding the Posted Interrupt supporting to Xen: Posted Interrupt allows vAPIC interrupts to inject into guest directly without any vmexit. - When delivering a interrupt to guest, if target vcpu is running, update Posted-interrupt requests bitmap and send a notification event to the vcpu. Then the vcpu will handle this

We seem to find an interesting bug, but not for sure. Each time before xen returns to hvm domain, it checks local_events_need_delivery to see whether any events pending and if yes, inject event by callback_irq into the virtual interrupt controller. However, the interesting point is, we never found any place, either in xen or in PV drivers, to clear evtchn_upcall_mask at any time. The initial

...id( *ebx = cpuid->ebx; *ecx = cpuid->ecx; *edx = cpuid->edx; - return; + break; } } - *eax = *ebx = *ecx = *edx = 0; + if ( input == 1 ) + *ecx |= 1U << (X86_FEATURE_HYPERVISOR % 32); } void vcpu_kick(struct vcpu *v) Index: 2008-10-27/xen/arch/x86/traps.c =================================================================== --- 2008-10-27.orig/xen/arch/x86/traps.c 2008-10-27 11:14:44.000000000 +0100 +++ 2008-10-27/xen/arch/x86/traps.c 2008-11-19 10:16:27.000000000 +0100 @@ -754,6 +754,7 @@ static...

Keir, It''s a resending patch for the timeout mechanism to deal with the shared interrupt issue for vt-d enabled hvm guest. We modify the patch following your comments last time and make some other small fix: 1) We don''t touch the locking around the hvm_dpci_eoi(). 2) Remove the HZ from the TIME_OUT_PERIOD macro which may confuse others. 3) Add some

...=============== --- 2006-10-04.orig/xen/include/asm-x86/event.h 2006-06-14 18:10:51.000000000 +0200 +++ 2006-10-04/xen/include/asm-x86/event.h 2006-10-04 15:11:04.000000000 +0200 @@ -9,6 +9,8 @@ #ifndef __ASM_EVENT_H__ #define __ASM_EVENT_H__ +#include <xen/shared.h> + static inline void vcpu_kick(struct vcpu *v) { /* @@ -28,7 +30,7 @@ static inline void vcpu_kick(struct vcpu static inline void vcpu_mark_events_pending(struct vcpu *v) { - if ( !test_and_set_bit(0, &v->vcpu_info->evtchn_upcall_pending) ) + if ( !test_and_set_bit(0, &vcpu_info(v, evtchn_upcall_pen...

...450 (XEN) [<ffff82c48014f989>] domain_relinquish_resources+0x1d9/0x270 (XEN) [<ffff82c48010611b>] domain_kill+0x7b/0x100 (XEN) [<ffff82c480103f54>] domctl_lock_acquire+0x44/0x70 (XEN) [<ffff82c48010465e>] do_domctl+0x4ae/0x1050 (XEN) [<ffff82c48014ab4d>] vcpu_kick+0x1d/0x80 (XEN) [<ffff82c48015d7b8>] get_page+0x28/0xf0 (XEN) [<ffff82c4801e9169>] syscall_enter+0xa9/0xae (XEN) (XEN) Pagetable walk from ffff8315ffffffe4: (XEN) L4[0x106] = 00000000cf56d027 5555555555555555 (XEN) L3[0x057] = 0000000000000000 ffffffffffffffff (XEN) (XEN) ******...

I last posted this back in April to critical acclaim (AKA near total silence). I''m not sure who looks after tools/include/xen-foreign. I had thought it was Jan but I think I was confused and was thinking of the semi-related xen/include/compat stuff. IOW I think nobody felt "responsible". Unless there''s any objection lets just treat this as coming under tools. The

This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.

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