mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: David Miller <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, acme@kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
	Namhyung Kim <namhyung@gmail.com>,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: perf's handling of unfindable user symbols...
Date: Wed, 17 Oct 2018 17:22:26 +0900	[thread overview]
Message-ID: <20181017172226.7274498db2bbe3431c3f4057@kernel.org> (raw)
In-Reply-To: <20181016184506.GB3254@redhat.com>

On Tue, 16 Oct 2018 15:45:06 -0300
Arnaldo Carvalho de Melo <acme@redhat.com> wrote:

> 
> So, I thought something had changed and in the past we would somehow
> find that address in the kallsyms, but I couldn't find anything to back
> that up, the patch introducing this is over a decade old, lots of things
> changed, so I was just thinking I was missing something.
> 
> I tried a gtod busy loop to generate vdso activity and added a 'perf
> probe' at that branch, on x86_64 to see if it ever gets hit:
> 
> Made thread__find_map() noinline, as 'perf probe' in lines of inline
> functions seems to not be working, only at function start. (Masami?)

Thank you for reporting it. Hmm, what happened when you did it?
I checked some points, but seems no problem.
(Would you see no line number? or defined event didn't work?)

Thank you,



-- 
Masami Hiramatsu <mhiramat@kernel.org>

  parent reply	other threads:[~2018-10-17  8:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-14  7:42 David Miller
2018-10-15 22:25 ` Arnaldo Carvalho de Melo
2018-10-15 23:02   ` David Miller
2018-10-16 18:45     ` Arnaldo Carvalho de Melo
2018-10-16 19:02       ` David Miller
2018-10-16 19:37         ` Arnaldo Carvalho de Melo
2018-10-17  8:22       ` Masami Hiramatsu [this message]
2018-10-17 12:28         ` Arnaldo Carvalho de Melo
2018-10-18  9:35           ` Masami Hiramatsu
2018-10-18  9:42           ` Masami Hiramatsu

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=20181017172226.7274498db2bbe3431c3f4057@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=davem@davemloft.net \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@gmail.com \
    --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
Powered by JetHome