From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753324AbbGBJ2d (ORCPT <rfc822;w@1wt.eu>);
	Thu, 2 Jul 2015 05:28:33 -0400
Received: from mail-wg0-f41.google.com ([74.125.82.41]:35060 "EHLO
	mail-wg0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752080AbbGBJ22 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 2 Jul 2015 05:28:28 -0400
Date: Thu, 2 Jul 2015 11:28:23 +0200
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
Message-ID: <20150702092823.GA11547@gmail.com>
References: <1435356140-31212-1-git-send-email-acme@kernel.org>
 <20150630045852.GB31981@gmail.com>
 <55924B2D.7000903@intel.com>
 <20150630105648.GA25749@gmail.com>
 <55929861.3050000@intel.com>
 <5593A29F.3080900@intel.com>
 <5593E147.1050803@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5593E147.1050803@intel.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* 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