Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: jpoimboe at redhat.com (Josh Poimboeuf)
Subject: [PATCH 2/4] x86/kprobes: Fix frame pointer annotations
Date: Thu, 9 May 2019 09:00:01 -0500	[thread overview]
Message-ID: <20190509140001.fvwzlnhai6ddqjmt@treble> (raw)
In-Reply-To: <20190509081431.GO2589@hirez.programming.kicks-ass.net>

On Thu, May 09, 2019 at 10:14:31AM +0200, Peter Zijlstra wrote:
> But what I'd love to do is something like the belwo patch, and make all
> the trampolines (very much including ftrace) use that. Such that we then
> only have 1 copy of this magic (well, 2 because x86_64 also needs an
> implementation of this of course).
> 
> Changing ftrace over to this would be a little more work but it can
> easily chain things a little to get its original context back:
> 
> ENTRY(ftrace_regs_caller)
> GLOBAL(ftrace_regs_func)
> 	push ftrace_stub
> 	push ftrace_regs_handler
> 	jmp call_to_exception_trampoline
> END(ftrace_regs_caller)
> 
> typedef void (*ftrace_func_t)(unsigned long, unsigned long, struct ftrace_op *, struct pt_regs *);
> 
> struct ftrace_regs_stack {
> 	ftrace_func_t func;
> 	unsigned long parent_ip;
> };
> 
> void ftrace_regs_handler(struct pr_regs *regs)
> {
> 	struct ftrace_regs_stack *st = (void *)regs->sp;
> 	ftrace_func_t func = st->func;
> 
> 	regs->sp += sizeof(long); /* pop func */
> 
> 	func(regs->ip, st->parent_ip, function_trace_op, regs);
> }
> 
> Hmm? I didn't look into the function_graph thing, but I imagine it can
> be added without too much pain.

I like this patch a lot, assuming it can be made to work for the
different users.

-- 
Josh

WARNING: multiple messages have this Message-ID (diff)
From: jpoimboe@redhat.com (Josh Poimboeuf)
Subject: [PATCH 2/4] x86/kprobes: Fix frame pointer annotations
Date: Thu, 9 May 2019 09:00:01 -0500	[thread overview]
Message-ID: <20190509140001.fvwzlnhai6ddqjmt@treble> (raw)
Message-ID: <20190509140001.xSmddJDE5umbQt1ahBITIBe7Bi6K7W_LharZSMTKv98@z> (raw)
In-Reply-To: <20190509081431.GO2589@hirez.programming.kicks-ass.net>

On Thu, May 09, 2019@10:14:31AM +0200, Peter Zijlstra wrote:
> But what I'd love to do is something like the belwo patch, and make all
> the trampolines (very much including ftrace) use that. Such that we then
> only have 1 copy of this magic (well, 2 because x86_64 also needs an
> implementation of this of course).
> 
> Changing ftrace over to this would be a little more work but it can
> easily chain things a little to get its original context back:
> 
> ENTRY(ftrace_regs_caller)
> GLOBAL(ftrace_regs_func)
> 	push ftrace_stub
> 	push ftrace_regs_handler
> 	jmp call_to_exception_trampoline
> END(ftrace_regs_caller)
> 
> typedef void (*ftrace_func_t)(unsigned long, unsigned long, struct ftrace_op *, struct pt_regs *);
> 
> struct ftrace_regs_stack {
> 	ftrace_func_t func;
> 	unsigned long parent_ip;
> };
> 
> void ftrace_regs_handler(struct pr_regs *regs)
> {
> 	struct ftrace_regs_stack *st = (void *)regs->sp;
> 	ftrace_func_t func = st->func;
> 
> 	regs->sp += sizeof(long); /* pop func */
> 
> 	func(regs->ip, st->parent_ip, function_trace_op, regs);
> }
> 
> Hmm? I didn't look into the function_graph thing, but I imagine it can
> be added without too much pain.

I like this patch a lot, assuming it can be made to work for the
different users.

-- 
Josh

  parent reply	other threads:[~2019-05-09 14:00 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08  7:49 [PATCH 0/4] x86: int3 fallout peterz
2019-05-08  7:49 ` Peter Zijlstra
2019-05-08  7:49 ` [PATCH 1/4] x86/entry/32: Clean up return from interrupt preemption path peterz
2019-05-08  7:49   ` Peter Zijlstra
2019-05-08  7:49 ` [PATCH 2/4] x86/kprobes: Fix frame pointer annotations peterz
2019-05-08  7:49   ` Peter Zijlstra
2019-05-08 11:54   ` jpoimboe
2019-05-08 11:54     ` Josh Poimboeuf
2019-05-08 12:04     ` peterz
2019-05-08 12:04       ` Peter Zijlstra
     [not found]       ` <20190508124248.u5ukpbhnh4wpiccq@treble>
     [not found]         ` <20190508153907.GM2589@hirez.programming.kicks-ass.net>
2019-05-08 18:48           ` jpoimboe
2019-05-08 18:48             ` Josh Poimboeuf
2019-05-09  1:20             ` mhiramat
2019-05-09  1:20               ` Masami Hiramatsu
2019-05-09  8:14               ` peterz
2019-05-09  8:14                 ` Peter Zijlstra
2019-05-09  9:27                 ` peterz
2019-05-09  9:27                   ` Peter Zijlstra
2019-05-09 14:00                 ` jpoimboe [this message]
2019-05-09 14:00                   ` Josh Poimboeuf
2019-05-09 14:01                 ` mhiramat
2019-05-09 14:01                   ` Masami Hiramatsu
2019-05-09 17:14                   ` peterz
2019-05-09 17:14                     ` Peter Zijlstra
2019-05-10  4:58                     ` mhiramat
2019-05-10  4:58                       ` Masami Hiramatsu
2019-05-10 12:31                       ` peterz
2019-05-10 12:31                         ` Peter Zijlstra
2019-05-11  0:52                         ` mhiramat
2019-05-11  0:52                           ` Masami Hiramatsu
2019-05-10 12:40                       ` peterz
2019-05-10 12:40                         ` Peter Zijlstra
2019-05-11  0:56                         ` mhiramat
2019-05-11  0:56                           ` Masami Hiramatsu
2019-05-13  8:15                           ` peterz
2019-05-13  8:15                             ` Peter Zijlstra
2019-05-09 16:20                 ` luto
2019-05-09 16:20                   ` Andy Lutomirski
2019-05-09 17:18                   ` peterz
2019-05-09 17:18                     ` Peter Zijlstra
2019-05-09 17:43                   ` rostedt
2019-05-09 17:43                     ` Steven Rostedt
2019-05-10  3:21                     ` mhiramat
2019-05-10  3:21                       ` Masami Hiramatsu
2019-05-10 12:14                       ` peterz
2019-05-10 12:14                         ` Peter Zijlstra
2019-05-10 12:17                       ` peterz
2019-05-10 12:17                         ` Peter Zijlstra
2019-05-10 14:54                         ` rostedt
2019-05-10 14:54                           ` Steven Rostedt
2019-05-09 17:37                 ` rostedt
2019-05-09 17:37                   ` Steven Rostedt
2019-05-09 18:26                   ` peterz
2019-05-09 18:26                     ` Peter Zijlstra
2019-05-09 18:36                     ` rostedt
2019-05-09 18:36                       ` Steven Rostedt
2019-05-08  7:49 ` [PATCH 3/4] x86/ftrace: Add pt_regs frame annotations peterz
2019-05-08  7:49   ` Peter Zijlstra
2019-05-08  7:49 ` [RFC][PATCH 4/4] x86_32: Provide consistent pt_regs peterz
2019-05-08  7:49   ` Peter Zijlstra
2019-05-08 11:57   ` jpoimboe
2019-05-08 11:57     ` Josh Poimboeuf
2019-05-08 20:58   ` torvalds
2019-05-08 20:58     ` Linus Torvalds

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=20190509140001.fvwzlnhai6ddqjmt@treble \
    --to=linux-kselftest@vger.kernel.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