All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86: use tzcnt instead of bsf
Date: Mon, 26 Jan 2015 09:49:22 +0000	[thread overview]
Message-ID: <54C60DA2.506@citrix.com> (raw)
In-Reply-To: <54C287670200007800059004@mail.emea.novell.com>

On 23/01/15 16:39, Jan Beulich wrote:
> Following a compiler change done in 2012, make use of the fact that for
> non-zero input BSF and TZCNT produce the same numeric result (EFLAGS
> setting differs), and that CPUs not knowing of TZCNT will treat the
> instruction as BSF (i.e. ignore what looks like a REP prefix to them).
> The assumption here is that TZCNT would never have worse performance
> than BSF.
>
> Also extend the asm() input in find_first_set_bit() to allow memory
> operands.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>

> ---
> Thanks to Andrew for noticing that I forgot to post this for Xen after
> a similar change got accepted into the Linux kernel.
>
> --- a/xen/arch/x86/bitops.c
> +++ b/xen/arch/x86/bitops.c
> @@ -62,7 +62,7 @@ unsigned int __find_first_zero_bit(
>          "   je 2f\n\t"
>          "   xor -"STR(BITS_PER_LONG/8)"(%2),%3\n\t"
>          "   jz 1b\n\t"
> -        "   bsf %3,%0\n\t"
> +        "   rep; bsf %3,%0\n\t"
>          "   lea -"STR(BITS_PER_LONG/8)"(%2),%2\n\t"
>          "2: sub %%ebx,%%edi\n\t"
>          "   shl $3,%%edi\n\t"
> --- a/xen/arch/x86/hvm/vpic.c
> +++ b/xen/arch/x86/hvm/vpic.c
> @@ -56,7 +56,7 @@ static int vpic_get_priority(struct hvm_
>          return VPIC_PRIO_NONE;
>  
>      /* prio = ffs(mask ROR vpic->priority_add); */
> -    asm ( "ror %%cl,%b1 ; bsf %1,%0"
> +    asm ( "ror %%cl,%b1 ; rep; bsf %1,%0"
>            : "=r" (prio) : "q" ((uint32_t)mask), "c" (vpic->priority_add) );
>      return prio;
>  }
> --- a/xen/include/asm-x86/bitops.h
> +++ b/xen/include/asm-x86/bitops.h
> @@ -382,7 +382,7 @@ static inline unsigned int __scanbit(uns
>   */
>  static inline unsigned int find_first_set_bit(unsigned long word)
>  {
> -    asm ( "bsf %1,%0" : "=r" (word) : "r" (word) );
> +    asm ( "rep; bsf %1,%0" : "=r" (word) : "rm" (word) );
>      return (unsigned int)word;
>  }
>  
>
>
>

      reply	other threads:[~2015-01-26  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 16:39 [PATCH] x86: use tzcnt instead of bsf Jan Beulich
2015-01-26  9:49 ` Andrew Cooper [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=54C60DA2.506@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xenproject.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.