similar to: [PATCH V2] libxc, libxenstore: make the headers C++-friendlier

Made the xenctrl.h and xenstore.h easier to use with C++: added ''extern "C"'' statements, moved the definition of enum xc_error_code above it''s typedef, and renamed a ''new'' parameter (''new'' is a C++ keyword). Includes a modification of _hvm_hw_fix_cpu() suggested by Jan Beulich. Signed-off-by: Razvan Cojocaru

XC_INVALID_PARAM such as asking for features unsupported by either xen or guest kernel. XC_OUT_OF_MEMORY no comment ;) Signed-off-by: Gerd Hoffmann <kraxel@suse.de> --- tools/libxc/xenctrl.h | 2 ++ 1 file changed, 2 insertions(+) Index: build-32-unstable-12802/tools/libxc/xenctrl.h =================================================================== ---

This patch adds new control messages for vcpu hotplug events. Via the xm vcpu_hotplug sub-program, VCPUS in domains can be enabled/disabled when CONFIG_HOTPLUG_CPU is enabled in the target domain''s kernel. Currently there is nothing that tracks whether a VCPU is up or down. My previous [1]patch added a new per-VCPU flag (VCPUF_down) which could be used to keep track of which VCPUS are

Implement tsc adjust feature IA32_TSC_ADJUST MSR is maintained separately for each logical processor. A logical processor maintains and uses the IA32_TSC_ADJUST MSR as follows: 1). On RESET, the value of the IA32_TSC_ADJUST MSR is 0; 2). If an execution of WRMSR to the IA32_TIME_STAMP_COUNTER MSR adds (or subtracts) value X from the TSC, the logical processor also adds (or subtracts) value X

--- src/guestfs-internal.h | 1 + src/libvirt-auth.c | 55 +++++++++++++++++++++++++++++++++++++++++--------- 2 files changed, 46 insertions(+), 10 deletions(-) diff --git a/src/guestfs-internal.h b/src/guestfs-internal.h index 5356920..d81fa6b 100644 --- a/src/guestfs-internal.h +++ b/src/guestfs-internal.h @@ -469,6 +469,7 @@ struct guestfs_h unsigned int nr_supported_credentials;

Following up on #190 [1], I''ve just added a simple patch that allows the manipulation of the TYPES hash from within the Merb module. Use like: Merb.add_mime_type(:png,%w[image/png]) Merb.remove_mime_type(:png) It specifically disallows the removal of the :all MimeType, since content negotiation relies on it. I''m not super wonderful at API design, so comments and

Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632 _______________________________________________ Xen-devel mailing list

Hi, All Intel QA conducted a full validation for xen 4.1 rc1, it includes VT-x, VT-d, SRIOV, RAS, TXT and xl tools testing. 24 issues were exposed. Refer the bug list, please. We already assigned 14 bugs to Intel developers (which has an ''Intel'' tag in the bug title), most of the rest 10 bugs are related xl command. For the these bugs, need community''s help to fix

about VIRQ &amp; PIRQ what is VIRQ  ?How VIRQ is different from PIRQ ?How VIRQ &amp; PIRQ are related each other ? DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any

I am trying to debug the Xen hypervisor from a second computer over the serial port, but nothing seems to work. Using mercurial, I got xen-3.2-testing.hg. I followed the steps in crashdb.txt in the docs/misc/ folder: set debug=y in Config.mk, crash_debug=y in xen/Rules.mk I also added -fno-omit-frame-pointer to these file as well. I compiled with no errors and booted with minicom connected to

From: Andrey Smetanin <asmetanin at virtuozzo.com> Synic is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI semantics - a message page in the guest memory with 16 256-byte per-SINT message slots - an event

This patchset implements the KVM part of the synthetic interrupt controller (synic) which is a building block of the Hyper-V paravirtualized device bus (vmbus). Synic is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI

This patchset implements the KVM part of the synthetic interrupt controller (synic) which is a building block of the Hyper-V paravirtualized device bus (vmbus). Synic is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI

This patchset implements the KVM part of the synthetic interrupt controller (SynIC) which is a building block of the Hyper-V paravirtualized device bus (vmbus). SynIC is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI

This patchset implements the KVM part of the synthetic interrupt controller (SynIC) which is a building block of the Hyper-V paravirtualized device bus (vmbus). SynIC is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI