The patch titled KVM: Fix asm constraints has been added to the -mm tree. Its filename is kvm-avoid-using-vmx-instruction-directly-fix-asm-constraints.patch See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: KVM: Fix asm constraints From: Avi Kivity <avi@xxxxxxxxxxxx> The change to directly encoded vmx opcodes (rather than asm instructions) forced us to pass the address of phys_addr as an operand, rather than its contents. However, nothing forces gcc to commit the contents of the variable to memory, so add an explicit "m" constraint. Signed-off-by: Avi Kivity <avi@xxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- drivers/kvm/kvm_main.c | 9 ++++++--- 1 files changed, 6 insertions(+), 3 deletions(-) diff -puN drivers/kvm/kvm_main.c~kvm-avoid-using-vmx-instruction-directly-fix-asm-constraints drivers/kvm/kvm_main.c --- a/drivers/kvm/kvm_main.c~kvm-avoid-using-vmx-instruction-directly-fix-asm-constraints +++ a/drivers/kvm/kvm_main.c @@ -368,7 +368,8 @@ static void vmcs_clear(struct vmcs *vmcs u8 error; asm volatile (ASM_VMX_VMCLEAR_RAX "; setna %0" - : "=g"(error) : "a"(&phys_addr) : "cc", "memory" ); + : "=g"(error) : "a"(&phys_addr), "m"(phys_addr) + : "cc", "memory"); if (error) printk(KERN_ERR "kvm: vmclear fail: %p/%llx\n", vmcs, phys_addr); @@ -411,7 +412,8 @@ static struct kvm_vcpu *__vcpu_load(stru per_cpu(current_vmcs, cpu) = vcpu->vmcs; asm volatile (ASM_VMX_VMPTRLD_RAX "; setna %0" - : "=g"(error) : "a"(&phys_addr) : "cc" ); + : "=g"(error) : "a"(&phys_addr), "m"(phys_addr) + : "cc"); if (error) printk(KERN_ERR "kvm: vmptrld %p/%llx fail\n", vcpu->vmcs, phys_addr); @@ -534,7 +536,8 @@ static __init void kvm_enable(void *garb /* enable and lock */ wrmsrl(MSR_IA32_FEATURE_CONTROL, old | 5); write_cr4(read_cr4() | CR4_VMXE); /* FIXME: not cpu hotplug safe */ - asm volatile (ASM_VMX_VMXON_RAX : : "a"(&phys_addr) : "memory", "cc"); + asm volatile (ASM_VMX_VMXON_RAX : : "a"(&phys_addr), "m"(phys_addr) + : "memory", "cc"); } static void kvm_disable(void *garbage) _ Patches currently in -mm which might be from avi@xxxxxxxxxxxx are kvm-userspace-interface.patch kvm-intel-virtual-mode-extensions-definitions.patch kvm-kvm-data-structures.patch kvm-random-accessors-and-constants.patch kvm-virtualization-infrastructure.patch kvm-virtualization-infrastructure-kvm-fix-guest-cr4-corruption.patch kvm-virtualization-infrastructure-include-desch.patch kvm-memory-slot-management.patch kvm-vcpu-creation-and-maintenance.patch kvm-workaround-cr0cd-cache-disable-bit-leak-from-guest-to.patch kvm-vcpu-execution-loop.patch kvm-define-exit-handlers.patch kvm-less-common-exit-handlers.patch kvm-mmu.patch kvm-x86-emulator.patch kvm-plumbing.patch kvm-dynamically-determine-which-msrs-to-load-and-save.patch kvm-fix-calculation-of-initial-value-of-rdx-register.patch kvm-avoid-using-vmx-instruction-directly.patch kvm-avoid-using-vmx-instruction-directly-fix-asm-constraints.patch kvm-fix-segment-state-changes-across-processor-mode-switches.patch kvm-fix-asm-constraints-for-segment-loads.patch kvm-segment-access-cleanup.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html