linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
	David Matlack <dmatlack@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	rkrcmar@redhat.com, haokexin@gmail.com, mpe@ellerman.id.au,
	yongjun_wei@trendmicro.com.cn, rusty@rustcorp.com.au,
	jbaron@akamai.com
Subject: Re: [PATCH 1/2] jump_labels: API for flushing deferred jump label updates
Date: Thu, 22 Dec 2016 13:35:50 +0100	[thread overview]
Message-ID: <87346b81-1905-4775-f745-388870fa2c96@redhat.com> (raw)
In-Reply-To: <20161219145819.GJ3107@twins.programming.kicks-ass.net>



On 19/12/2016 15:58, Peter Zijlstra wrote:
> On Fri, Dec 16, 2016 at 02:30:35PM -0800, David Matlack wrote:
>> Modules that use static_key_deferred need a way to synchronize with
>> any delayed work that is still pending when the module is unloaded.
>> Introduce static_key_deferred_flush() which flushes any pending
>> jump label updates.
> 
> Makes sense I suppose.
> 
> It also appears I forgot to provide new style APIs for this
> functionality as I completely forgot about it for it lives in its own
> file :-/
> 
> In any case,
> 
> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>

Thanks, I'll merge these through the KVM tree.

Paolo

      reply	other threads:[~2016-12-22 12:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 22:30 [PATCH 1/2] jump_labels: API for flushing deferred jump label updates David Matlack
2016-12-16 22:30 ` [PATCH 2/2] KVM: x86: flush pending lapic jump label updates on module unload David Matlack
2016-12-19 14:24   ` Radim Krčmář
2016-12-19 14:58 ` [PATCH 1/2] jump_labels: API for flushing deferred jump label updates Peter Zijlstra
2016-12-22 12:35   ` Paolo Bonzini [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=87346b81-1905-4775-f745-388870fa2c96@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dmatlack@google.com \
    --cc=haokexin@gmail.com \
    --cc=jbaron@akamai.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=peterz@infradead.org \
    --cc=rkrcmar@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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).