[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100825213654.GF14874@lenovo>
Date: Thu, 26 Aug 2010 01:36:54 +0400
From: Cyrill Gorcunov <gorcunov@...il.com>
To: Don Zickus <dzickus@...hat.com>
Cc: Ingo Molnar <mingo@...e.hu>,
Robert Richter <robert.richter@....com>,
Peter Zijlstra <peterz@...radead.org>,
Lin Ming <ming.m.lin@...el.com>,
"fweisbec@...il.com" <fweisbec@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Huang, Ying" <ying.huang@...el.com>,
Yinghai Lu <yinghai@...nel.org>,
Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH -v3] perf, x86: try to handle unknown nmis with running
perfctrs
On Wed, Aug 25, 2010 at 05:20:37PM -0400, Don Zickus wrote:
...
> The only problem is only one counter is overflowing in these cases, so we
> would have to do it all the time, which may not be hard. But I was
> thinking of something similar.
>
> For now, I am trying to force counter0 off, seeing that most of the perf
> errata on nehalem have been on counter0. Or maybe I can get 'perf top' to
> use something other than counter0 by running 'perf record' first?
>
> Cheers,
> Don
>
> >
> > -- Cyrill
>
Well, I never looked deep inside perf tool code itself. Perhaps the easiest
(if you want to disable counter0) is just disable it in kernel and see how
it goes, no?
-- Cyrill
--
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