From: Peter Zijlstra <peterz@infradead.org>
To: changbin.du@intel.com
Cc: akpm@linux-foundation.org, tglx@linutronix.de,
pombredanne@nexb.com, neilb@suse.com,
linux-kernel@vger.kernel.org, jpoimboe@redhat.com
Subject: Re: [PATCH] scripts/faddr2line: show the code context
Date: Tue, 29 May 2018 18:03:32 +0200 [thread overview]
Message-ID: <20180529160332.GD12258@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1521444205-2259-1-git-send-email-changbin.du@intel.com>
On Mon, Mar 19, 2018 at 03:23:25PM +0800, changbin.du@intel.com wrote:
> From: Changbin Du <changbin.du@intel.com>
>
> Inspired by gdb command 'list', show the code context of target lines.
> Here is a example:
>
> $ scripts/faddr2line vmlinux native_write_msr+0x6
> native_write_msr+0x6/0x20:
> arch_static_branch at arch/x86/include/asm/msr.h:105
> 100 return EAX_EDX_VAL(val, low, high);
> 101 }
> 102
> 103 static inline void notrace __wrmsr(unsigned int msr, u32 low, u32 high)
> 104 {
> 105 asm volatile("1: wrmsr\n"
> 106 "2:\n"
> 107 _ASM_EXTABLE_HANDLE(1b, 2b, ex_handler_wrmsr_unsafe)
> 108 : : "c" (msr), "a"(low), "d" (high) : "memory");
> 109 }
> 110
> (inlined by) static_key_false at include/linux/jump_label.h:142
> 137 #define JUMP_TYPE_LINKED 2UL
> 138 #define JUMP_TYPE_MASK 3UL
> 139
> 140 static __always_inline bool static_key_false(struct static_key *key)
> 141 {
> 142 return arch_static_branch(key, false);
> 143 }
> 144
> 145 static __always_inline bool static_key_true(struct static_key *key)
> 146 {
> 147 return !arch_static_branch(key, true);
> (inlined by) native_write_msr at arch/x86/include/asm/msr.h:150
> 145 static inline void notrace
> 146 native_write_msr(unsigned int msr, u32 low, u32 high)
> 147 {
> 148 __wrmsr(msr, low, high);
> 149
> 150 if (msr_tracepoint_active(__tracepoint_write_msr))
> 151 do_trace_write_msr(msr, ((u64)high << 32 | low), 0);
> 152 }
> 153
> 154 /* Can be uninlined because referenced by paravirt */
> 155 static inline int notrace
Not a fan of this :-/ And you didn't even make it optional. Nor did you
Cc the original author of the tool.
next prev parent reply other threads:[~2018-05-29 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 7:23 changbin.du
2018-05-29 16:03 ` Peter Zijlstra [this message]
2018-05-29 16:26 ` Peter Zijlstra
2018-05-29 17:07 ` Josh Poimboeuf
2018-05-29 17:24 ` Peter Zijlstra
2018-05-29 17:25 ` Peter Zijlstra
2018-05-29 22:01 ` NeilBrown
2018-06-04 2:06 ` Du, Changbin
2018-06-04 2:10 ` Du, Changbin
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=20180529160332.GD12258@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=changbin.du@intel.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--cc=pombredanne@nexb.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
all inboxes | Powered by JetHome®