From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Jason Baron <jbaron@akamai.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
boris.ostrovsky@oracle.com, david.vrabel@citrix.com
Subject: Re: Regression :-) Re: [GIT PULL RESEND] x86/jumpmplabel changes for v3.12-rc1
Date: Wed, 11 Sep 2013 14:01:13 -0400 [thread overview]
Message-ID: <20130911180113.GB29406@phenom.dumpdata.com> (raw)
In-Reply-To: <20130911135237.245386fb@gandalf.local.home>
On Wed, Sep 11, 2013 at 01:52:37PM -0400, Steven Rostedt wrote:
> On Wed, 11 Sep 2013 13:25:52 -0400
> Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
>
>
> > commit 97ce2c88f9ad42e3c60a9beb9fca87abf3639faa
> > Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> > Date: Wed Oct 12 16:17:54 2011 -0700
> >
> > jump-label: initialize jump-label subsystem much earlier
> >
> > Initialize jump_labels much, much earlier, so they're available for use
> > during system setup.
> >
> > Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> > Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> >
> >
> > implies that yes.
>
> Unfortunately it does not. All that patch did was move
> jump_label_init() up more. If anything, it implies "no".
>
> The question is, can we enable jump_labels before jump_label_init()?
>
> Note, we may still be able to (as it seems to work), the thing is, the
> only thing that static_key_slow_inc() does is to tell jump_label_init()
> to enable it. Before jump_label_init() is called, nothing has changed.
> No code modification, all users of paravirt_ticketlocks_enabled are
> still off.
<confused>
I am thins would still work:
47 static __always_inline void arch_spin_unlock(arch_spinlock_t *lock)
148 {
149 if (TICKET_SLOWPATH_FLAG &&
150 static_key_false(¶virt_ticketlocks_enabled)) {
(from arch/x86/include/asm/spinlock.h) as the static_key_false
would check the key->enabled. Which had been incremented?
Granted there are no patching done yet, but that should still allow
this code path to be taken?
next prev parent reply other threads:[~2013-09-11 18:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 2:48 [GIT PULL RESEND] x86/jumpmplabel changes for v3.12-rc1 H. Peter Anvin
2013-09-11 13:47 ` Regression :-) " Konrad Rzeszutek Wilk
2013-09-11 13:57 ` Steven Rostedt
2013-09-11 13:57 ` Konrad Rzeszutek Wilk
2013-09-11 14:25 ` Konrad Rzeszutek Wilk
2013-09-11 14:56 ` Steven Rostedt
2013-09-11 15:21 ` Konrad Rzeszutek Wilk
2013-09-11 15:47 ` Steven Rostedt
2013-09-11 16:17 ` Konrad Rzeszutek Wilk
2013-09-11 17:05 ` Steven Rostedt
2013-09-11 17:25 ` Konrad Rzeszutek Wilk
2013-09-11 17:52 ` Steven Rostedt
2013-09-11 18:01 ` Konrad Rzeszutek Wilk [this message]
2013-09-11 18:26 ` Steven Rostedt
2013-09-11 18:56 ` Konrad Rzeszutek Wilk
2013-09-11 19:14 ` Steven Rostedt
2013-09-11 19:55 ` Konrad Rzeszutek Wilk
2013-09-12 16:13 ` Steven Rostedt
2013-09-11 14:38 ` Steven Rostedt
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=20130911180113.GB29406@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jbaron@akamai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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