From: Prarit Bhargava <prarit@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH v2] x86, bitops, variable_test_bit should return 1 not -1 on a match
Date: Wed, 07 Oct 2015 19:27:17 -0400 [thread overview]
Message-ID: <5615AA55.5000203@redhat.com> (raw)
In-Reply-To: <1440440579-7535-1-git-send-email-prarit@redhat.com>
re-ping on this. Just making sure this wasn't dropped on the floor.
P.
On 08/24/2015 02:22 PM, Prarit Bhargava wrote:
> This issue was noticed while debugging a CPU hotplug issue. On x86
> with (NR_CPUS > 1) the cpu_online() define is cpumask_test_cpu().
> cpumask_test_cpu() should return 1 if the cpu is set in cpumask and
> 0 otherwise.
>
> However, cpumask_test_cpu() returns -1 if the cpu in the cpumask is
> set and 0 otherwise. This happens because cpumask_test_cpu() calls
> test_bit() which is a define that will call variable_test_bit().
>
> variable_test_bit() calls the assembler instruction sbb (Subtract
> with Borrow, " Subtracts the source from the destination, and subtracts 1
> extra if the Carry Flag is set. Results are returned in "dest".)
>
> A bit match results in -1 being returned from variable_test_bit() if a
> match occurs, not 1 as the function is supposed to.
>
> It looks like the code never does, for example, (test_bit() == 1) so this
> change should not have any impact.
>
> [v2]: hpa: Use setc, (Set if Carry, "Sets the byte in the operand to 1 if
> the Carry Flag is set, otherwise sets the operand to 0.") instead of !!
>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: x86@kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
> ---
> arch/x86/include/asm/bitops.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/include/asm/bitops.h b/arch/x86/include/asm/bitops.h
> index cfe3b95..c0bff87 100644
> --- a/arch/x86/include/asm/bitops.h
> +++ b/arch/x86/include/asm/bitops.h
> @@ -313,10 +313,10 @@ static __always_inline int constant_test_bit(long nr, const volatile unsigned lo
>
> static inline int variable_test_bit(long nr, volatile const unsigned long *addr)
> {
> - int oldbit;
> + u8 oldbit;
>
> asm volatile("bt %2,%1\n\t"
> - "sbb %0,%0"
> + "setc %0"
> : "=r" (oldbit)
> : "m" (*(unsigned long *)addr), "Ir" (nr));
>
>
next prev parent reply other threads:[~2015-10-07 23:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 17:18 [PATCH] x86, bitops, variable_test_bit should return 1 not -1 on a match Prarit Bhargava
2015-08-21 6:51 ` Ingo Molnar
2015-08-21 8:08 ` H. Peter Anvin
2015-08-21 11:53 ` Prarit Bhargava
2015-08-24 18:22 ` [PATCH v2] " Prarit Bhargava
2015-10-07 23:27 ` Prarit Bhargava [this message]
2015-10-08 8:51 ` Ingo Molnar
2015-10-08 11:48 ` [PATCH] " Prarit Bhargava
2015-08-21 11:50 ` Prarit Bhargava
2015-08-22 9:14 ` Ingo Molnar
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=5615AA55.5000203@redhat.com \
--to=prarit@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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 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).