Avi Kivity wrote: >> Or gcc >> might move the assignment of phys_addr to after the inline assembly. >> > "asm volatile" prevents that (and I'm not 100% sure it's necessary). No, it won't necessarily. "asm volatile" simply forces gcc to emit the assembler, even if it thinks its output doesn't get used. It makes no ordering guarantees with respect to other code (or even other "asm volatiles"). The "memory" clobbers should fix the ordering of the asms though. J - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [kvm-devel] [PATCH] KVM: Avoid using vmx instruction directly
- From: "H. Peter Anvin" <[email protected]>
- Re: [kvm-devel] [PATCH] KVM: Avoid using vmx instruction directly
- From: "Martin Schwidefsky" <[email protected]>
- Re: [kvm-devel] [PATCH] KVM: Avoid using vmx instruction directly
- References:
- [PATCH] KVM: Avoid using vmx instruction directly
- From: Avi Kivity <[email protected]>
- Re: [kvm-devel] [PATCH] KVM: Avoid using vmx instruction directly
- From: Arnd Bergmann <[email protected]>
- Re: [kvm-devel] [PATCH] KVM: Avoid using vmx instruction directly
- From: Avi Kivity <[email protected]>
- Re: [kvm-devel] [PATCH] KVM: Avoid using vmx instruction directly
- From: Arnd Bergmann <[email protected]>
- Re: [kvm-devel] [PATCH] KVM: Avoid using vmx instruction directly
- From: Avi Kivity <[email protected]>
- [PATCH] KVM: Avoid using vmx instruction directly
- Prev by Date: [patch 08/19] i386: cleanup apic code
- Next by Date: [patch 09/19] i386: Convert to clock event devices
- Previous by thread: Re: [kvm-devel] [PATCH] KVM: Avoid using vmx instruction directly
- Next by thread: Re: [kvm-devel] [PATCH] KVM: Avoid using vmx instruction directly
- Index(es):