mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Wang Nan <wangnan0@huawei.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Ingo Molnar <mingo@kernel.org>, David Ahern <dsahern@gmail.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Intel PT not work on 4.5.0-rc
Date: Thu, 25 Feb 2016 23:59:46 +0200	[thread overview]
Message-ID: <56CF7952.2030904@intel.com> (raw)
In-Reply-To: <20160225142105.GL8720@kernel.org>

On 25/02/2016 4:21 p.m., Arnaldo Carvalho de Melo wrote:
> Hi Adrian,
>
> 	While fixing a problem I introducing in parsing 'intel_pt//',
> i.e. the empty '//' part, which is fixed in my perf/core by now, I tried
> using intel_pt with 4.5.0-rc4 and couldn't get any trace :-\
>
> 	Talking with Jiri he tried it on his side, also a Broadwell
> machine, and it worked, same tooling (acme/perf/core) but with a fedora
> kernel, 4.3.5-200.fc22.x86_64.
>
> 	Later I'll try switching to the kernel Jiri is using to see if it works
> for me with that one.
>
> 	I'm busy now and this Broadwell machine is my main workstation,
> can you check if you reproduce this problem?

I am on vacation until some time next week.  I will try to look at
it before then but might not manage it.

>
> [root@jouet ~]# perf --version
> perf version 4.5.rc4.gbb109a
> [root@jouet ~]# perf record -e intel_pt//u -a sleep 10
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 1.767 MB perf.data ]
> [root@jouet ~]# perf evlist -v
> intel_pt//u: type: 7, size: 112, config: 0x400, { sample_period, sample_freq }: 1, sample_type: IP|TID|TIME|CPU|IDENTIFIER, read_format: ID, disabled: 1, inherit: 1, exclude_kernel: 1, exclude_hv: 1, sample_id_all: 1
> dummy:u: type: 1, size: 112, config: 0x9, { sample_period, sample_freq }: 1, sample_type: IP|TID|TIME|CPU|IDENTIFIER, read_format: ID, disabled: 1, inherit: 1, exclude_kernel: 1, exclude_hv: 1, mmap: 1, comm: 1, task: 1, sample_id_all: 1, mmap2: 1, comm_exec: 1, context_switch: 1
> [root@jouet ~]# perf script
> [root@jouet ~]#
>
>  From 'perf report -D'
>
> 0x1a8 [0x88]: event: 70
> .
> . ... raw event: size 136 bytes
> .  0000:  46 00 00 00 00 00 88 00 01 00 00 00 00 00 00 00  F...............
> .  0010:  07 00 00 00 00 00 00 00 1f 00 00 00 00 00 00 00  ................
> .  0020:  14 01 58 31 00 00 00 00 69 84 20 d9 d5 3b 00 00  ..X1....i. ..;..
> .  0030:  01 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00  ................
> .  0040:  00 08 00 00 00 00 00 00 03 00 00 00 00 00 00 00  ................
> .  0050:  00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00  ................
> .  0060:  00 02 00 00 00 00 00 00 00 c0 03 00 00 00 00 00  ................
> .  0070:  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
> .  0080:  02 00 00 00 00 00 00 00                          ........
>
> 0x1a8 [0x88]: PERF_RECORD_AUXTRACE_INFO type: 1
>    PMU Type            7
>    Time Shift          31
>    Time Muliplier      827851028
>    Time Zero           65789656859753
>    Cap Time Zero       1
>    TSC bit             0x400
>    NoRETComp bit       0x800
>    Have sched_switch   3
>    Snapshot mode       0
>    Per-cpu maps        1
>    MTC bit             0x200
>    TSC:CTC numerator   0
>    TSC:CTC denominator 0
>    CYC bit             0x2
>
> [root@jouet ~]# perf report -D | tail -13
> Aggregated stats: (excludes AUX area (e.g. instruction trace) decoded / synthesized events)
>             TOTAL events:      21753
>              MMAP events:        130
>              COMM events:        596
>              EXIT events:          2
>              FORK events:        594
>             MMAP2 events:       8541

There ought to be AUX events here, so it looks like no data has been captured,
so a problem with recording.

>      ITRACE_START events:          4
>   SWITCH_CPU_WIDE events:      11882
>    FINISHED_ROUND events:          3
>     AUXTRACE_INFO events:          1
> intel_pt//u stats:
> dummy:u stats:
> [root@jouet ~]#
>

  reply	other threads:[~2016-02-25 22:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 14:21 Arnaldo Carvalho de Melo
2016-02-25 21:59 ` Adrian Hunter [this message]
2016-03-01 15:40   ` Adrian Hunter
2016-03-01 15:59     ` Arnaldo Carvalho de Melo
2016-03-01 18:20       ` Arnaldo Carvalho de Melo
2016-03-01 18:24         ` Arnaldo Carvalho de Melo
2016-03-01 19:12           ` 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=56CF7952.2030904@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=wangnan0@huawei.com \
    /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