linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Milian Wolff <milian.wolff@kdab.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	perf group <linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH] perf tools: Add dedicated unwind addr_space member into thread struct
Date: Wed, 06 Apr 2016 23:15:27 +0200	[thread overview]
Message-ID: <2529332.MbcSn26IoS@agathebauer> (raw)
In-Reply-To: <20160406154657.GA14971@krava.brq.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2194 bytes --]

On Mittwoch, 6. April 2016 17:46:57 CEST Jiri Olsa wrote:
> On Tue, Apr 05, 2016 at 10:35:24AM +0200, Jiri Olsa wrote:
> > On Mon, Apr 04, 2016 at 11:17:11PM +0200, Milian Wolff wrote:
> > 
> > SNIP
> > 
> > >             7f688a5ef0c4 usleep (/usr/lib/libc-2.23.so)
> > >             5582244227cd main (/tmp/ex_sleep)
> > >   
> > >   1001.702 ( 0.059 ms): ex_sleep/4390 nanosleep(rqtp: 0x7ffe4d16eec0
> > > 
> > > ) = 0
> > > 
> > >                   20379e syscall_slow_exit_work ([kernel.kallsyms])
> > >                   203bc4 syscall_return_slowpath ([kernel.kallsyms])
> > >                   797248 int_ret_from_sys_call ([kernel.kallsyms])
> > >             
> > >             7f688a5c5600 __nanosleep (/usr/lib/libc-2.23.so)
> > >             7f688a5ef0c4 usleep (/usr/lib/libc-2.23.so)
> > >             5582244227d7 main (/tmp/ex_sleep)
> > > 
> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > 
> > > Is there a way to increase the event buffer or something like that to
> > > not lose events when the costly dwarf unwinding happens for the first
> > > time? Consecutive unwinding is cached by libunwind and much faster.
> > 
> > not sure about perf trace, but there's -m option available for perf record
> > that allows you to increase the buffer size
> > 
> > > Alternatively, I could try to unwind in the `sys_enter`, but then I'd
> > > need to buffer the output to print the trace after the duration line...
> > > 
> > > How would you guys handle this situation?
> > > 
> > > Also, Jiri, Arnaldo - what would be your suggestion on how to handle the
> > > `thread::priv` situation - I doubt my naive `priv2` approach is
> > > acceptable.
> > 
> > yea, I think one priv is more than enough ;-)
> > 
> > I think we want to move the the unwinder usage of this field into separate
> > field
> need to run test over this, but will try to post it this week
> let me know if this solution would work for you

Yes, works for me, thanks a lot!

Feel free to add

    Tested-by: Milian Wolff <milian.wolff@kdab.com>

-- 
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]

  reply	other threads:[~2016-04-08 11:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 20:39 perf trace report with time consumed Milian Wolff
2016-03-30 14:53 ` Arnaldo Carvalho de Melo
2016-03-30 21:24   ` Milian Wolff
2016-03-30 21:58     ` Arnaldo Carvalho de Melo
2016-03-31 22:34       ` Milian Wolff
2016-04-01 13:01         ` Arnaldo Carvalho de Melo
2016-04-03 16:30           ` Jiri Olsa
2016-04-03 18:46         ` Milian Wolff
2016-04-04  6:14           ` Jiri Olsa
2016-04-04 21:17             ` Milian Wolff
2016-04-05  8:35               ` Jiri Olsa
2016-04-06 15:46                 ` [PATCH] perf tools: Add dedicated unwind addr_space member into thread struct Jiri Olsa
2016-04-06 21:15                   ` Milian Wolff [this message]
2016-04-08 12:58                     ` Arnaldo Carvalho de Melo
2016-04-06 21:16                 ` perf trace report with time consumed Milian Wolff
2016-04-08 13:01                   ` Arnaldo Carvalho de Melo

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=2529332.MbcSn26IoS@agathebauer \
    --to=milian.wolff@kdab.com \
    --cc=acme@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-perf-users@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;
as well as URLs for NNTP newsgroup(s).