All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, Rusty Russell <rusty@rustcorp.com.au>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 1/2] x86/bitops: implement __test_bit
Date: Mon, 31 Aug 2015 09:59:47 +0200	[thread overview]
Message-ID: <20150831075947.GA9974@gmail.com> (raw)
In-Reply-To: <20150831105355-mutt-send-email-mst@redhat.com>


* Michael S. Tsirkin <mst@redhat.com> wrote:

> On Sun, Aug 30, 2015 at 11:13:20PM -0700, H. Peter Anvin wrote:
> > Presumably because gcc can't generate bt... whether or not it is worth it is another matter.
> > 
> > On August 30, 2015 11:05:49 PM PDT, Ingo Molnar <mingo@kernel.org> wrote:
> > >
> > >* Michael S. Tsirkin <mst@redhat.com> wrote:
> > >
> > >> +static __always_inline int __constant_test_bit(long nr, const
> > >unsigned long *addr)
> > >> +{
> > >> +	return ((1UL << (nr & (BITS_PER_LONG-1))) &
> > >> +		(addr[nr >> _BITOPS_LONG_SHIFT])) != 0;
> > >> +}
> > >> +
> > >> +static inline int __variable_test_bit(long nr, const unsigned long
> > >*addr)
> > >> +{
> > >> +	int oldbit;
> > >> +
> > >> +	asm volatile("bt %2,%1\n\t"
> > >> +		     "sbb %0,%0"
> > >> +		     : "=r" (oldbit)
> > >> +		     : "m" (*addr), "Ir" (nr));
> > >> +
> > >> +	return oldbit;
> > >> +}
> > >
> > >Color me confused, why use assembly for this at all?
> > >
> > >Why not just use C for testing the bit (i.e. turn __constant_test_bit()
> > >into 
> > >__test_bit()) - that would also allow the compiler to propagate the
> > >result, 
> > >potentially more optimally than we can do it via SBB...
> > >
> > >Thanks,
> > >
> > >	Ingo
> 
> Exactly:
> 
> 
> Disassembly of section .text:
> 
> 00000000 <__variable_test_bit>:
> __variable_test_bit():
>    0:   8b 54 24 08             mov    0x8(%esp),%edx
>    4:   8b 44 24 04             mov    0x4(%esp),%eax
>    8:   0f a3 02                bt     %eax,(%edx)
>    b:   19 c0                   sbb    %eax,%eax
>    d:   c3                      ret    
>    e:   66 90                   xchg   %ax,%ax
> 
> 00000010 <__constant_test_bit>:
> __constant_test_bit():
>   10:   8b 4c 24 04             mov    0x4(%esp),%ecx
>   14:   8b 44 24 08             mov    0x8(%esp),%eax
>   18:   89 ca                   mov    %ecx,%edx
>   1a:   c1 fa 04                sar    $0x4,%edx
>   1d:   8b 04 90                mov    (%eax,%edx,4),%eax
>   20:   d3 e8                   shr    %cl,%eax
>   22:   83 e0 01                and    $0x1,%eax
>   25:   c3                      ret    

But that's due to the forced interface of generating a return code. Please compare 
it at an inlined usage site, where GCC is free to do the comparison directly and 
use the result in flags.

Thanks,

	Ingo

  reply	other threads:[~2015-08-31  7:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-30  8:38 [PATCH 1/2] x86/bitops: implement __test_bit Michael S. Tsirkin
2015-08-30  8:38 ` [PATCH 2/2] kvm/x86: use __test_bit Michael S. Tsirkin
2015-08-31  6:05 ` [PATCH 1/2] x86/bitops: implement __test_bit Ingo Molnar
2015-08-31  6:13   ` H. Peter Anvin
2015-08-31  7:56     ` Michael S. Tsirkin
2015-08-31  7:59       ` Ingo Molnar [this message]
2015-08-31  8:15         ` yalin wang
2015-08-31  8:19           ` Ingo Molnar
2015-08-31  8:15         ` Ingo Molnar
2015-08-31 11:19         ` Michael S. Tsirkin
2015-09-01  9:24           ` Ingo Molnar
2015-09-01  9:40             ` Michael S. Tsirkin
2015-09-01 11:39               ` Ingo Molnar
2015-09-01 15:03                 ` Michael S. Tsirkin
2015-09-01 23:48                   ` 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=20150831075947.GA9974@gmail.com \
    --to=mingo@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mst@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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.