linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Gleb Natapov <gleb@redhat.com>,
	Linux KVM mailing list <kvm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86, kvm: Remove incorrect redundant assembly constraint
Date: Mon, 26 Nov 2012 08:22:45 +0100	[thread overview]
Message-ID: <50B318C5.8090508@redhat.com> (raw)
In-Reply-To: <1353537681-18759-1-git-send-email-hpa@linux.intel.com>

Il 21/11/2012 23:41, H. Peter Anvin ha scritto:
> From: "H. Peter Anvin" <hpa@linux.intel.com>
> 
> In __emulate_1op_rax_rdx, we use "+a" and "+d" which are input/output
> constraints, and *then* use "a" and "d" as input constraints.  This is
> incorrect, but happens to work on some versions of gcc.
> 
> However, it breaks gcc with -O0 and icc, and may break on future
> versions of gcc.
> 
> Reported-and-tested-by: Melanie Blower <melanie.blower@intel.com>
> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
> Link: http://lkml.kernel.org/r/B3584E72CFEBED439A3ECA9BCE67A4EF1B17AF90@FMSMSX107.amr.corp.intel.com
> ---
>  arch/x86/kvm/emulate.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
> index 39171cb..bba39bf 100644
> --- a/arch/x86/kvm/emulate.c
> +++ b/arch/x86/kvm/emulate.c
> @@ -426,8 +426,7 @@ static void invalidate_registers(struct x86_emulate_ctxt *ctxt)
>  			_ASM_EXTABLE(1b, 3b)				\
>  			: "=m" ((ctxt)->eflags), "=&r" (_tmp),		\
>  			  "+a" (*rax), "+d" (*rdx), "+qm"(_ex)		\
> -			: "i" (EFLAGS_MASK), "m" ((ctxt)->src.val),	\
> -			  "a" (*rax), "d" (*rdx));			\
> +			: "i" (EFLAGS_MASK), "m" ((ctxt)->src.val));	\
>  	} while (0)
>  
>  /* instruction has only one source operand, destination is implicit (e.g. mul, div, imul, idiv) */
> 

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

  reply	other threads:[~2012-11-26  7:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 19:45 PROBLEM: compilation issue, inline assembly arch/x86/kvm/emulate.c fails at -O0 Blower, Melanie
2012-11-15  0:14 ` H. Peter Anvin
2012-11-15 15:09   ` Blower, Melanie
2012-11-21 21:35 ` H. Peter Anvin
2012-11-21 22:31   ` Blower, Melanie
2012-11-21 22:41 ` [PATCH] x86, kvm: Remove incorrect redundant assembly constraint H. Peter Anvin
2012-11-26  7:22   ` Paolo Bonzini [this message]
2012-11-26 22:48     ` H. Peter Anvin
2012-11-26 23:48       ` Marcelo Tosatti
2012-11-26 23:49         ` H. Peter Anvin
2012-11-27  0:53           ` Marcelo Tosatti
2012-11-27  0:01 ` [tip:x86/urgent] " tip-bot for H. Peter Anvin

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=50B318C5.8090508@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=hpa@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=tglx@linutronix.de \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).