mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Networking <netdev@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"ast@kernel.org" <ast@kernel.org>,
	"daniel@iogearbox.net" <daniel@iogearbox.net>,
	Kernel Team <Kernel-team@fb.com>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"acme@redhat.com" <acme@redhat.com>,
	"jolsa@kernel.org" <jolsa@kernel.org>,
	"namhyung@kernel.org" <namhyung@kernel.org>
Subject: Re: [PATCH v5 perf,bpf 12/15] perf, bpf: enable annotation of bpf program
Date: Mon, 4 Mar 2019 20:43:25 +0000	[thread overview]
Message-ID: <F363AFC6-A048-44C7-80DE-22C20ADE7CD8@fb.com> (raw)
In-Reply-To: <20190304203713.GC2563@krava>



> On Mar 4, 2019, at 12:37 PM, Jiri Olsa <jolsa@redhat.com> wrote:
> 
> On Mon, Mar 04, 2019 at 07:45:00PM +0000, Song Liu wrote:
>> 
>> 
>>> On Mar 4, 2019, at 5:53 AM, Jiri Olsa <jolsa@redhat.com> wrote:
>>> 
>>> On Wed, Feb 27, 2019 at 09:06:40PM -0800, Song Liu wrote:
>>> 
>>> SNIP
>>> 
>>>> +	fflush(s);
>>>> +	do {
>>>> +		const struct bpf_line_info *linfo = NULL;
>>>> +		struct disasm_line *dl;
>>>> +		size_t prev_buf_size;
>>>> +		const char *srcline;
>>>> +		u64 addr;
>>>> +
>>>> +		addr = pc + ((u64 *)(info_linear->info.jited_ksyms))[sub_id];
>>>> +		count = disassemble(pc, &info);
>>>> +
>>>> +		if (prog_linfo)
>>>> +			linfo = bpf_prog_linfo__lfind_addr_func(prog_linfo,
>>>> +								addr, sub_id,
>>>> +								nr_skip);
>>>> +
>>>> +		if (linfo && btf) {
>>>> +			srcline = btf__name_by_offset(btf, linfo->line_off);
>>>> +			nr_skip++;
>>>> +		} else
>>>> +			srcline = NULL;
>>>> +
>>>> +		fprintf(s, "\n");
>>>> +		prev_buf_size = buf_size;
>>>> +		fflush(s);
>>>> +
>>>> +		if (!opts->hide_src_code && srcline) {
>>>> +			args->offset = -1;
>>> 
>>> why's the offset not needed in here?
>> 
>> This is the source code line. Based on my understanding of annotation
>> code, we put -1 for source code line. Did I misunderstand something?
> 
> please double check, IIRC annotation_line__print will print
> just more info if offset is present, together with the source,
> but I haven't checked that code for some time, so I might be wrong
> 
> jirka

In symbol__parse_objdump_line(), default offset is -1. And it is only 
updated if line_ip is not -1. And line_ip for src code line is -1, so 
offset for the source line is -1. 

It works fine in the tests when I toggle source code on/off with key
's'. 

Thanks
Song


  reply	other threads:[~2019-03-04 20:44 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28  5:06 [PATCH v5 perf,bpf 00/15] perf annotation of BPF programs Song Liu
2019-02-28  5:06 ` [PATCH v5 perf,bpf 01/15] perf, bpf: consider events with attr.bpf_event as side-band events Song Liu
2019-02-28  5:06 ` [PATCH v5 perf,bpf 02/15] bpf: libbpf: introduce bpf_program__get_prog_info_linear() Song Liu
2019-02-28  5:06 ` [PATCH v5 perf,bpf 03/15] bpf: bpftool: use bpf_program__get_prog_info_linear() in prog.c:do_dump() Song Liu
2019-02-28  5:06 ` [PATCH v5 perf,bpf 04/15] perf, bpf: synthesize bpf events with bpf_program__get_prog_info_linear() Song Liu
2019-02-28  5:06 ` [PATCH v5 perf,bpf 05/15] perf: change prototype of perf_event__synthesize_bpf_events() Song Liu
2019-02-28  5:06 ` [PATCH v5 perf,bpf 06/15] perf, bpf: save bpf_prog_info in a rbtree in perf_env Song Liu
2019-02-28  5:06 ` [PATCH v5 perf,bpf 07/15] perf, bpf: save bpf_prog_info information as headers to perf.data Song Liu
2019-03-04 13:52   ` Jiri Olsa
2019-03-04 19:36     ` Song Liu
2019-03-04 20:23       ` Jiri Olsa
2019-03-04 20:31         ` Song Liu
2019-03-04 13:52   ` Jiri Olsa
2019-03-04 13:52   ` Jiri Olsa
2019-03-04 19:41     ` Song Liu
2019-03-04 20:37       ` Jiri Olsa
2019-03-04 13:52   ` Jiri Olsa
2019-02-28  5:06 ` [PATCH v5 perf,bpf 08/15] perf, bpf: save btf in a rbtree in perf_env Song Liu
2019-03-04 13:52   ` Jiri Olsa
2019-03-04 19:43     ` Song Liu
2019-03-04 20:31       ` Jiri Olsa
2019-03-04 13:53   ` Jiri Olsa
2019-02-28  5:06 ` [PATCH v5 perf,bpf 09/15] perf, bpf: save btf information as headers to perf.data Song Liu
2019-03-04 13:52   ` Jiri Olsa
2019-02-28  5:06 ` [PATCH v5 perf,bpf 10/15] perf-top: add option --no-bpf-event Song Liu
2019-02-28  5:06 ` [PATCH v5 perf,bpf 11/15] perf: add -lopcodes to feature-libbfd Song Liu
2019-02-28  5:06 ` [PATCH v5 perf,bpf 12/15] perf, bpf: enable annotation of bpf program Song Liu
2019-03-04 13:52   ` Jiri Olsa
2019-03-04 13:53   ` Jiri Olsa
2019-03-04 20:52     ` Song Liu
2019-03-04 13:53   ` Jiri Olsa
2019-03-04 19:45     ` Song Liu
2019-03-04 20:37       ` Jiri Olsa
2019-03-04 20:43         ` Song Liu [this message]
2019-02-28  5:06 ` [PATCH v5 perf,bpf 13/15] perf, bpf: process PERF_BPF_EVENT_PROG_LOAD for annotation Song Liu
2019-03-04 13:53   ` Jiri Olsa
2019-02-28  5:06 ` [PATCH v5 perf,bpf 14/15] perf: introduce side band thread Song Liu
2019-02-28  5:06 ` [PATCH v5 perf,bpf 15/15] perf, bpf: save bpf_prog_info and btf of short living bpf programs Song Liu

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=F363AFC6-A048-44C7-80DE-22C20ADE7CD8@fb.com \
    --to=songliubraving@fb.com \
    --cc=Kernel-team@fb.com \
    --cc=acme@redhat.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®