From: Ingo Molnar <mingo@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/8] perf/pt -> Intel PT/BTS
Date: Thu, 2 Jul 2015 11:28:23 +0200 [thread overview]
Message-ID: <20150702092823.GA11547@gmail.com> (raw)
In-Reply-To: <5593E147.1050803@intel.com>
* Adrian Hunter <adrian.hunter@intel.com> wrote:
> I am going to need to know what hardware it is and cpu feature flags i.e.
> /proc/cpuinfo
>
> Also ls /sys/bus/event_source/devices
Sorry about the delay, the merge window is busier than usual ...
So I tried it on:
1) Intel box, old kernel, new tools: threw an error
2) AMD box, new kernel, new tools: threw an error
3) AMD box, old kernel, new tools: threw an error
failure was expected in all 3 cases, but it threw the exact same error with no
real indication about what the problem was, while the real problem was different
for each case:
1) good CPU, bad kernel
2) bad CPU, good kernel
3) bad CPU, bad kernel
I'd expect the 'good CPU, good kernel' combination to work:
4) Intel box, new kernel, new tools
... but haven't tried it yet.
Thanks,
Ingo
next prev parent reply other threads:[~2015-07-02 9:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 22:02 [GIT PULL 0/8] perf/pt -> Intel PT/BTS Arnaldo Carvalho de Melo
2015-06-26 22:02 ` [PATCH 1/8] perf auxtrace: Add Intel PT as an AUX area tracing type Arnaldo Carvalho de Melo
2015-06-26 22:02 ` [PATCH 2/8] perf tools: Add Intel PT packet decoder Arnaldo Carvalho de Melo
2015-06-26 22:02 ` [PATCH 3/8] perf tools: Add Intel PT instruction decoder Arnaldo Carvalho de Melo
2015-06-26 22:02 ` [PATCH 4/8] perf tools: Add Intel PT log Arnaldo Carvalho de Melo
2015-06-26 22:02 ` [PATCH 5/8] perf tools: Add Intel PT decoder Arnaldo Carvalho de Melo
2015-06-26 22:02 ` [PATCH 6/8] perf tools: Add Intel PT support Arnaldo Carvalho de Melo
2015-06-26 22:02 ` [PATCH 7/8] perf tools: Take Intel PT into use Arnaldo Carvalho de Melo
2015-06-26 22:02 ` [PATCH 8/8] perf tools: Add Intel BTS support Arnaldo Carvalho de Melo
2015-06-30 4:58 ` [GIT PULL 0/8] perf/pt -> Intel PT/BTS Ingo Molnar
2015-06-30 7:54 ` Adrian Hunter
2015-06-30 10:56 ` Ingo Molnar
2015-06-30 13:23 ` Adrian Hunter
2015-06-30 14:39 ` Arnaldo Carvalho de Melo
2015-07-01 8:19 ` Adrian Hunter
2015-07-01 12:47 ` Adrian Hunter
2015-07-02 9:28 ` Ingo Molnar [this message]
2015-07-02 9:43 ` Ingo Molnar
2015-07-02 12:35 ` Adrian Hunter
2015-07-02 13:02 ` Arnaldo Carvalho de Melo
2015-07-02 19:00 ` Ingo Molnar
2015-07-03 9:08 ` Adrian Hunter
2015-07-03 14:31 ` Alexander Shishkin
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=20150702092823.GA11547@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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