similar to: [PATCH 0 of 7] Miscellaneous updates

Looks like you added some more type problems which break the 64-bit build. Signed-of-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff -r 668cf7d7cc8c xenalyze.c --- a/xenalyze.c Thu May 06 16:27:50 2010 -0500 +++ b/xenalyze.c Fri May 07 16:22:10 2010 -0700 @@ -4382,8 +4382,8 @@ if ( opt.dump_all ) printf(" %s npf gpa %llx q %x mfn %llx t %d\n",

Hi, I''m a PhD student trying to add some load balancing code to the credit scheduler in order to fit some specific necessities. I''m trying to understand the credit scheduler code and I don''t quite get in which part of it a pcpu starts running a vcpu. I need to keep track of when a vpcu starts running in a cpu and when it stops. Any hint on that? I think that it would

Hi all, I need a periodic timer running at ideally at 125 microseconds and at least 500 microseconds. I''ve just found the VCPUOP_set_periodic_timer, however there is a comment saying "periods less than one millisecond may not be supported". I will be running on an x64 machine. Is this supported? If not, is there any alternate means of generating a fast interrupt? Regards.

Hi, I am having a hard time figuring out how to have logon scripts that only execute if the user is a member of a certain group. I had the smart idea of putting the supplemental logon script in a share only available to the group, and then calling it from the normal logon script using "CALL "path_to_script". However it looks like it always executes that CALL even if the user

Hi, I just added 32GB memory in my system and wanted Xen to see that memory, so enabled PAE in xen0 and XenU. I did a make menuconfig in xen0 and xenU, then did a make in xen-unstable and a make install. Whilebooting this kernel, I get the above error PAE mode mismatch. I looked under xen/include/asm-x86/processor.h has #define X86_CR4_PAE defined and so does cpufeature.h have this defined.

After adding the configuration bit: deny message = invalid recipient domains = +local_domains !verify = recipient/callout=no_cache from: http://wiki2.dovecot.org/LMTP/Exim <http://wiki2.dovecot.org/LMTP/Exim> running update-exim4.conf and service exim4 restart the server is still accepting emails to recipients that do not exist in dovecot. Any ideas?

We saw these issues in recent ChangeSet: 1. Reboot fail in Guest OS: Reboot in guest will close current qemu windows but does not create a new qemu window to restart 32bit HV/xen0: 2. 4 LTP math cases(float_bessel, float_exp_log, float_power and float_trigo) sometime fail. (775) 3. Kernel build in VMX may meet kernel panic. It complains like: "<0> Kernel panic - not syncing:

We (Michael Fetterman, George Dunlap and I) have been working over the last while on a full replacement for Xen''s shadow pagetable support. This mail contains some design notes, below; a patch against xen-unstable, giving a snapshot of the current state of the new shadow code, is at http://www.cl.cam.ac.uk/~tjd21/shadow2.patch Comments on both are welcome, although the code is not

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.

From: Zhang Xiantao <xiantao.zhang@intel.com> With virtual EPT support, L1 hyerpvisor can use EPT hardware for L2 guest''s memory virtualization. In this way, L2 guest''s performance can be improved sharply. According to our testing, some benchmarks can show > 5x performance gain. Signed-off-by: Zhang Xiantao <xiantao.zhang@intel.com> Zhang Xiantao (11):

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 05 Oct 2018 19:38:52 +0100 Source: xen Binary: xenstore-utils xen-utils-common xen-hypervisor-common xen-doc xen-utils-4.11 xen-hypervisor-4.11-amd64 xen-system-amd64 xen-hypervisor-4.11-arm64 xen-system-arm64 xen-hypervisor-4.11-armhf xen-system-armhf libxen-dev libxenmisc4.11 libxencall1 libxendevicemodel1

The self_nmi() code cause''s an NMI to be triggered by sending an APIC message to the local processor. However, NMIs are blocked by the VMEXIT, until the next iret or VMENTER. Volume 3 Chapter 27 Section 1 of the Intel SDM states: An NMI causes subsequent NMIs to be blocked, but only after the VM exit completes. As a result, as soon as the VMENTER happens, an immediate VMEXIT happens