From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Jason Baron <jbaron@redhat.com>
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
hpa@zytor.com, mingo@elte.hu, davem@davemloft.net,
ddaney.cavm@gmail.com, pjt@google.com, rth@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4][RFC] jump label: introduce default true branch
Date: Wed, 21 Dec 2011 20:49:40 +0100 [thread overview]
Message-ID: <1324496980.17070.1.camel@twins> (raw)
In-Reply-To: <cover.1324493360.git.jbaron@redhat.com>
On Wed, 2011-12-21 at 14:09 -0500, Jason Baron wrote:
> Hi Peter,
>
> I've introduced a new static_branch_def_true() construct, such that the straight
> line path is the true branch, and we patch a jump to get to the false branch.
> I think this patch series should address the issues that came up with sched_feat()
> implementation.
Nice trick, I've only casually read patch 1 because my brain gave up for
the day, but I'll have a closer look tomorrow.
next prev parent reply other threads:[~2011-12-21 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 19:09 [PATCH 0/4][RFC] jump label: introduce default true branch Jason Baron
2011-12-21 19:09 ` [PATCH 1/4] jump label: Introduce default true branch + API update Jason Baron
2011-12-21 19:09 ` [PATCH 2/4] perf: Make use of updated jump label API Jason Baron
2011-12-21 19:09 ` [PATCH 3/4] tracepoints: update to use new " Jason Baron
2011-12-21 19:09 ` [PATCH 4/4] sched: Make use of " Jason Baron
2011-12-21 19:49 ` Peter Zijlstra [this message]
2012-02-20 22:47 ` [PATCH 0/4][RFC] jump label: introduce default true branch H. Peter Anvin
2012-02-20 22:51 ` Peter Zijlstra
2012-02-21 14:35 ` Jason Baron
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=1324496980.17070.1.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=ddaney.cavm@gmail.com \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=rth@redhat.com \
/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.