From: Sean Christopherson <seanjc@google.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: kvm@vger.kernel.org, x86@kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] x86/uaccess: Improve __try_cmpxchg64_user_asm for x86_32
Date: Mon, 16 May 2022 18:16:16 +0000 [thread overview]
Message-ID: <YoKU8IBa37WwIgex@google.com> (raw)
In-Reply-To: <20220515203713.635980-1-ubizjak@gmail.com>
On Sun, May 15, 2022, Uros Bizjak wrote:
> Improve __try_cmpxcgh64_user_asm for !CONFIG_CC_HAS_ASM_GOTO_TIED_OUTPUT
> by relaxing the output register constraint from "c" to "q" constraint,
> which allows the compiler to choose between %ecx or %ebx register.
>
> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
> Cc: Sean Christopherson <seanjc@google.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> ---
> arch/x86/include/asm/uaccess.h | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/include/asm/uaccess.h b/arch/x86/include/asm/uaccess.h
> index 35f222aa66bf..9fae2a1cc267 100644
> --- a/arch/x86/include/asm/uaccess.h
> +++ b/arch/x86/include/asm/uaccess.h
> @@ -448,7 +448,7 @@ do { \
>
> #ifdef CONFIG_X86_32
> /*
> - * Unlike the normal CMPXCHG, hardcode ECX for both success/fail and error.
> + * Unlike the normal CMPXCHG, use output GPR for both success/fail and error.
> * There are only six GPRs available and four (EAX, EBX, ECX, and EDX) are
> * hardcoded by CMPXCHG8B, leaving only ESI and EDI. If the compiler uses
> * both ESI and EDI for the memory operand, compilation will fail if the error
> @@ -461,11 +461,12 @@ do { \
> __typeof__(*(_ptr)) __new = (_new); \
> asm volatile("\n" \
> "1: " LOCK_PREFIX "cmpxchg8b %[ptr]\n" \
> - "mov $0, %%ecx\n\t" \
> - "setz %%cl\n" \
> + "mov $0, %[result]\n\t" \
> + "setz %b[result]\n" \
> "2:\n" \
> - _ASM_EXTABLE_TYPE_REG(1b, 2b, EX_TYPE_EFAULT_REG, %%ecx) \
> - : [result]"=c" (__result), \
> + _ASM_EXTABLE_TYPE_REG(1b, 2b, EX_TYPE_EFAULT_REG, \
> + %[result]) \
Huh. I remember trying this, but either I could never get one of these formats
correct (most likely) or I got sidetracked by the clang-13 bug and never circled
back to allowing EBX.
Regardless, clang-13 and gcc-11 are happy with this,
Reviewed-by: Sean Christopherson <seanjc@google.com>
> + : [result] "=q" (__result), \
> "+A" (__old), \
> [ptr] "+m" (*_ptr) \
> : "b" ((u32)__new), \
> --
> 2.35.1
>
prev parent reply other threads:[~2022-05-16 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 20:37 [PATCH] x86/uaccess: Improve __try_cmpxchg64_user_asm for x86_32 Uros Bizjak
2022-05-16 18:16 ` Sean Christopherson [this message]
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=YoKU8IBa37WwIgex@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=ubizjak@gmail.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.