mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] jump_labels: fix concurrent static_key_enable/disable()
Date: Tue, 1 Aug 2017 18:46:18 +0200	[thread overview]
Message-ID: <dacd77dc-3c6c-e0c2-089f-30c91f17c392@redhat.com> (raw)
In-Reply-To: <20170801164520.5a56wrieijlwgyds@hirez.programming.kicks-ass.net>

On 01/08/2017 18:45, Peter Zijlstra wrote:
> 
> Thanks for doing these patches, I hadn't come around to them yet.
> 
> On Tue, Aug 01, 2017 at 05:24:04PM +0200, Paolo Bonzini wrote:
>>  
>> +void static_key_enable(struct static_key *key)
>> +{
>> +	STATIC_KEY_CHECK_USE();
>> +	if (atomic_read(&key->enabled) > 0) {
>> +		WARN_ON_ONCE(atomic_read(&key->enabled) != 1);
>> +		return;
>> +	}
>> +
>> +	cpus_read_lock();
>> +	jump_label_lock();
>> +	if (atomic_read(&key->enabled) == 0) {
>> +		atomic_set(&key->enabled, -1);
>> +		jump_label_update(key);
> 
> As per the previous discussion, should I do a patch adding barriers here
> (or using atomic_set_release()) such that we close the window where a
> concurrent inc/enable sees 1 but not all text changes?

Sure, and that applies to static_key_slow_inc as well.

Paolo

>> +		atomic_set(&key->enabled, 1);
>> +	}
>> +	jump_label_unlock();
>> +	cpus_read_unlock();
>> +}
>> +EXPORT_SYMBOL_GPL(static_key_enable);

  reply	other threads:[~2017-08-01 16:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 15:24 [PATCH 0/3] jump_labels: concurrency fixes Paolo Bonzini
2017-08-01 15:24 ` [PATCH 1/3] jump_labels: fix concurrent static_key_enable/disable() Paolo Bonzini
2017-08-01 16:45   ` Peter Zijlstra
2017-08-01 16:46     ` Paolo Bonzini [this message]
2017-08-10 12:12   ` [tip:locking/core] jump_label: Fix " tip-bot for Paolo Bonzini
2017-08-01 15:24 ` [PATCH 2/3] jump_labels: do not use unserialized static_key_enabled Paolo Bonzini
2017-08-01 20:52   ` Eric Dumazet
2017-08-02  5:45     ` Paolo Bonzini
2017-08-10 12:12   ` [tip:locking/core] jump_label: Do not use unserialized static_key_enabled() tip-bot for Paolo Bonzini
2017-08-01 15:24 ` [PATCH 3/3] cpuset: make nr_cpusets private Paolo Bonzini
2017-08-02  1:08   ` Zefan Li
2017-08-10 12:13   ` [tip:locking/core] cpuset: Make " tip-bot for Paolo Bonzini

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=dacd77dc-3c6c-e0c2-089f-30c91f17c392@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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

Powered by JetHome