From: David Daney <ddaney@caviumnetworks.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Roland McGrath <roland@redhat.com>,
Mark Wielaard <mjw@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
Julien Desfossez <julien.desfossez@polymtl.ca>,
dominique.toupin@ericsson.com, ltt-dev@lists.casi.polymtl.ca,
systemtap@sources.redhat.com, linux-kernel@vger.kernel.org,
Jason Baron <jbaron@redhat.com>,
hpa@zytor.com, rostedt@goodmis.org, mingo@elte.hu,
tglx@linutronix.de, andi@firstfloor.org, rth@redhat.com,
masami.hiramatsu.pt@hitachi.com, fweisbec@gmail.com,
avi@redhat.com, davem@davemloft.net, sam@ravnborg.org,
michael@ellerman.id.au, Peter Zijlstra <peterz@infradead.org>
Subject: Re: Porting "jump labels" to userspace
Date: Wed, 16 Feb 2011 12:14:28 -0800 [thread overview]
Message-ID: <4D5C3024.6040807@caviumnetworks.com> (raw)
In-Reply-To: <20110216200034.GA6066@Krystal>
On 02/16/2011 12:00 PM, Mathieu Desnoyers wrote:
[...]>
> Actually, creating the equivalent of the jump labels for userspace is on our
> list of "things to do" for the UST project.
>
> If Jason and other jump label contributors agree to dual-license the jump label
> generic and per-arch implementations under both GPLv2 and LGPLv2.1, we could
> probably re-use a large part of this code to create a static jump label library
> for userspace. The concerned authors are precisely: Jason for generic and x86
> code, Steven for some improvements in generic code and David S. Miller for the
> sparc port. After things settle down with the current jump label changes
> proposed by Peter Zijlstra, we might also want to ask for his permission to
> LGPLize his changes.
>
FWIW: MIPS jump label support is now in as of:
94bb0c1 (MIPS: jump label: Add MIPS support.)
I would be the author of that.
David Daney
next prev parent reply other threads:[~2011-02-16 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D5AA164.1050607@polymtl.ca>
[not found] ` <y0mvd0ltgba.fsf@fche.csb>
[not found] ` <AANLkTi=Nsy6fXE9=Njxs9LPHuohHzf=q5kD+fK765Rht@mail.gmail.com>
[not found] ` <1297853778.3224.90.camel@springer.wildebeest.org>
[not found] ` <20110216185056.CAD7B1806E0@magilla.sf.frob.com>
2011-02-16 20:00 ` Porting "jump labels" to userspace (was: Re: [ltt-dev] LTTng-UST vs SystemTap userspace tracing benchmarks) Mathieu Desnoyers
2011-02-16 20:04 ` Roland McGrath
2011-02-16 20:17 ` Porting "jump labels" to userspace David Daney
2011-02-16 20:39 ` Mathieu Desnoyers
2011-02-16 20:45 ` Thomas Gleixner
2011-02-16 21:42 ` Peter Zijlstra
2011-02-17 13:58 ` Ingo Molnar
2011-02-16 20:14 ` David Daney [this message]
2011-02-16 20:36 ` Mathieu Desnoyers
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=4D5C3024.6040807@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=dominique.toupin@ericsson.com \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=julien.desfossez@polymtl.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=michael@ellerman.id.au \
--cc=mingo@elte.hu \
--cc=mjw@redhat.com \
--cc=peterz@infradead.org \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=rth@redhat.com \
--cc=sam@ravnborg.org \
--cc=stefanha@gmail.com \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
/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.