[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150702092823.GA11547@gmail.com>
Date: Thu, 2 Jul 2015 11:28:23 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Adrian Hunter <adrian.hunter@...el.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
linux-kernel@...r.kernel.org, Jiri Olsa <jolsa@...hat.com>,
David Ahern <dsahern@...il.com>,
Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Stephane Eranian <eranian@...gle.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [GIT PULL 0/8] perf/pt -> Intel PT/BTS
* Adrian Hunter <adrian.hunter@...el.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists