From: Peter Zijlstra <peterz@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>,
Andrey Konovalov <andreyknvl@google.com>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH tip/master v4] kprobes: extable: Identify kprobes' insn-slots as kernel text area
Date: Tue, 10 Jan 2017 09:59:23 +0100 [thread overview]
Message-ID: <20170110085923.GD3092@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20170109173648.k7dxu7nz22qc6upq@treble>
On Mon, Jan 09, 2017 at 11:36:48AM -0600, Josh Poimboeuf wrote:
> BTW, I think we'll have more problems with generated code if/when we
> move to an x86 DWARF unwinder, because it won't have any idea how to
> unwind past generated code. Long term I wonder if it would make sense
> to create some kind of framework for creating or registering generated
> code, so we can solve these types of problems in a single place.
Yes, this seems like a good idea. Maybe we could pull the rbtree thing
from modules and make that a more generic interface for code
registration.
next prev parent reply other threads:[~2017-01-10 8:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 6:42 Detecting kprobes generated code addresses Josh Poimboeuf
2016-12-25 3:13 ` Masami Hiramatsu
2016-12-25 6:16 ` Masami Hiramatsu
2016-12-26 4:30 ` Masami Hiramatsu
2016-12-26 14:50 ` [PATCH tip/master] kprobes: extable: Identify kprobes' insn-slots as kernel text area Masami Hiramatsu
2016-12-26 15:34 ` [PATCH tip/master v2] " Masami Hiramatsu
2016-12-26 17:21 ` kbuild test robot
2016-12-26 17:46 ` kbuild test robot
2016-12-27 6:13 ` Masami Hiramatsu
2016-12-27 6:14 ` [PATCH tip/master v3] " Masami Hiramatsu
2017-01-03 10:54 ` Peter Zijlstra
2017-01-04 5:06 ` Masami Hiramatsu
2017-01-04 10:01 ` Peter Zijlstra
2017-01-08 4:22 ` Masami Hiramatsu
2017-01-08 12:31 ` Masami Hiramatsu
2017-01-08 14:58 ` [PATCH tip/master v4] " Masami Hiramatsu
2017-01-09 17:36 ` Josh Poimboeuf
2017-01-10 1:11 ` Masami Hiramatsu
2017-01-10 8:59 ` Peter Zijlstra [this message]
2017-01-10 21:42 ` Josh Poimboeuf
2017-01-11 9:57 ` Masami Hiramatsu
2017-01-14 9:56 ` [tip:perf/core] kprobes, extable: Identify kprobes trampolines " tip-bot for Masami Hiramatsu
2017-01-04 14:21 ` [PATCH tip/master v3] kprobes: extable: Identify kprobes' insn-slots " 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=20170110085923.GD3092@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ananth@linux.vnet.ibm.com \
--cc=andreyknvl@google.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@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 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).