All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	peterz@infradead.org, torvalds@linux-foundation.org,
	konrad.wilk@oracle.com, pbonzini@redhat.com,
	paulmck@linux.vnet.ibm.com, waiman.long@hp.com, davej@redhat.com,
	x86@kernel.org, jeremy@goop.org, paul.gortmaker@windriver.com,
	ak@linux.intel.com, jasowang@redhat.com,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	xen-devel@lists.xenproject.org, riel@redhat.com,
	borntraeger@de.ibm.com, akpm@linux-foundation.org,
	a.ryabinin@samsung.com, sasha.levin@oracle.com,
	dave@stgolabs.net
Subject: Re: [PATCH V3] x86 spinlock: Fix memory corruption on completing completions
Date: Thu, 12 Feb 2015 19:55:42 +0530	[thread overview]
Message-ID: <54DCB7E6.8040802@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150212140248.GA11050@redhat.com>

On 02/12/2015 07:32 PM, Oleg Nesterov wrote:
> Damn, sorry for noise, forgot to mention...
>
> On 02/12, Raghavendra K T wrote:
>>
>> +static inline void __ticket_check_and_clear_slowpath(arch_spinlock_t *lock,
>> +							__ticket_t head)
>> +{
>> +	if (head & TICKET_SLOWPATH_FLAG) {
>> +		arch_spinlock_t old, new;
>> +
>> +		old.tickets.head = head;
>> +		new.tickets.head = head & ~TICKET_SLOWPATH_FLAG;
>> +		old.tickets.tail = new.tickets.head + TICKET_LOCK_INC;
>> +		new.tickets.tail = old.tickets.tail;
>> +
>> +		/* try to clear slowpath flag when there are no contenders */
>> +		cmpxchg(&lock->head_tail, old.head_tail, new.head_tail);
>> +	}
>> +}
>
> ...
>
>> +clear_slowpath:
>> +	if (TICKET_SLOWPATH_FLAG)
>> +		__ticket_check_and_clear_slowpath(lock, inc.head);
>
> I think you can remove this "if (TICKET_SLOWPATH_FLAG)" check. If it is
> defined as zero, gcc should optimize out the code under "if (head & 0)".
>

right, the above if ( ) is unnecesary, though we would have same code
at the end, getting rid of that makes code more clean.

  parent reply	other threads:[~2015-02-12 14:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 11:47 [PATCH V3] x86 spinlock: Fix memory corruption on completing completions Raghavendra K T
2015-02-12 11:47 ` Raghavendra K T
2015-02-12 11:47 ` Raghavendra K T
2015-02-12 13:37 ` Oleg Nesterov
2015-02-12 13:37 ` Oleg Nesterov
2015-02-12 13:37   ` Oleg Nesterov
2015-02-12 14:21   ` Raghavendra K T
2015-02-12 14:21   ` Raghavendra K T
2015-02-12 14:21   ` Raghavendra K T
2015-02-12 13:50 ` Oleg Nesterov
2015-02-12 13:50   ` Oleg Nesterov
2015-02-12 14:23   ` Raghavendra K T
2015-02-12 14:23     ` Raghavendra K T
2015-02-12 14:23   ` Raghavendra K T
2015-02-12 13:50 ` Oleg Nesterov
2015-02-12 14:02 ` Oleg Nesterov
2015-02-12 14:02 ` Oleg Nesterov
2015-02-12 14:02   ` Oleg Nesterov
2015-02-12 14:25   ` Raghavendra K T
2015-02-12 14:25   ` Raghavendra K T
2015-02-12 14:25   ` Raghavendra K T [this message]
2015-02-12 15:00 ` Peter Zijlstra
2015-02-12 15:00 ` Peter Zijlstra
2015-02-12 15:00   ` Peter Zijlstra
2015-02-12 15:28   ` Raghavendra K T
2015-02-12 15:28   ` Raghavendra K T
2015-02-12 15:28   ` Raghavendra K T
  -- strict thread matches above, loose matches on Subject: below --
2015-02-12 11:47 Raghavendra K T

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=54DCB7E6.8040802@linux.vnet.ibm.com \
    --to=raghavendra.kt@linux.vnet.ibm.com \
    --cc=a.ryabinin@samsung.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=borntraeger@de.ibm.com \
    --cc=dave@stgolabs.net \
    --cc=davej@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jasowang@redhat.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=oleg@redhat.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=sasha.levin@oracle.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=waiman.long@hp.com \
    --cc=x86@kernel.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.