LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: avi@qumranet.com (Avi Kivity), torvalds@osdl.org
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
akpm@osdl.org, mingo@elte.hu
Subject: Re: [PATCH 4/5] KVM: Fix asm constraints with CONFIG_FRAME_POINTER=n
Date: Tue, 23 Jan 2007 14:10:00 +1100 [thread overview]
Message-ID: <E1H9C2q-0006ZQ-00@gondolin.me.apana.org.au> (raw)
In-Reply-To: <20070111100630.55461250595@il.qumranet.com>
Avi Kivity <avi@qumranet.com> wrote:
> A "g" constraint may place a local variable in an %rsp-relative memory operand.
> but if your assembly changes %rsp, the operand points to the wrong location.
>
> An "r" constraint fixes that.
>
> Thanks to Ingo Molnar for neatly bisecting the problem.
>
> Signed-off-by: Avi Kivity <avi@qumranet.com>
>
> Index: linux-2.6/drivers/kvm/vmx.c
> ===================================================================
> --- linux-2.6.orig/drivers/kvm/vmx.c
> +++ linux-2.6/drivers/kvm/vmx.c
> @@ -1825,7 +1825,7 @@ again:
> #endif
> "setbe %0 \n\t"
> "popf \n\t"
> - : "=g" (fail)
> + : "=r" (fail)
> : "r"(vcpu->launched), "d"((unsigned long)HOST_RSP),
> "c"(vcpu),
> [rax]"i"(offsetof(struct kvm_vcpu, regs[VCPU_REGS_RAX])),
We need the following fix for 2.6.20.
[KVM] vmx: Fix register constraint in launch code
Both "=r" and "=g" breaks my build on i386:
$ make
CC [M] drivers/kvm/vmx.o
{standard input}: Assembler messages:
{standard input}:3318: Error: bad register name `%sil'
make[1]: *** [drivers/kvm/vmx.o] Error 1
make: *** [_module_drivers/kvm] Error 2
The reason is that setbe requires an 8-bit register but "=r" does not
constrain the target register to be one that has an 8-bit version on
i386.
According to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10153
the correct constraint is "=q".
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
diff --git a/drivers/kvm/vmx.c b/drivers/kvm/vmx.c
index ce219e3..0aa2659 100644
--- a/drivers/kvm/vmx.c
+++ b/drivers/kvm/vmx.c
@@ -1824,7 +1824,7 @@ again:
#endif
"setbe %0 \n\t"
"popf \n\t"
- : "=g" (fail)
+ : "=q" (fail)
: "r"(vcpu->launched), "d"((unsigned long)HOST_RSP),
"c"(vcpu),
[rax]"i"(offsetof(struct kvm_vcpu, regs[VCPU_REGS_RAX])),
next prev parent reply other threads:[~2007-01-23 3:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 10:02 [PATCH 0/5] KVM updates for 2.6.20 Avi Kivity
2007-01-11 10:03 ` [PATCH 1/5] KVM: Make sure there is a vcpu context loaded when destroying the mmu Avi Kivity
2007-01-11 10:04 ` [PATCH 2/5] KVM: Fix race between mmio reads and injected interrupts Avi Kivity
2007-01-11 10:05 ` [PATCH 3/5] KVM: x86 emulator: fix bit string instructions Avi Kivity
2007-01-11 10:06 ` [PATCH 4/5] KVM: Fix asm constraints with CONFIG_FRAME_POINTER=n Avi Kivity
2007-01-23 3:10 ` Herbert Xu [this message]
2007-01-11 10:07 ` [PATCH 5/5] KVM: Fix bogus pagefault on writable pages Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1H9C2q-0006ZQ-00@gondolin.me.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=akpm@osdl.org \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.org \
--subject='Re: [PATCH 4/5] KVM: Fix asm constraints with CONFIG_FRAME_POINTER=n' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).