[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120621132914.GA24632@erda.amd.com>
Date: Thu, 21 Jun 2012 15:29:14 +0200
From: Robert Richter <robert.richter@....com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
CC: Luming Yu <luming.yu@...il.com>,
LKML <linux-kernel@...r.kernel.org>, <tglx@...utronix.de>,
<sfr@...b.auug.org.au>, Andrew Morton <akpm@...ux-foundation.org>,
<jcm@...masters.org>, <linux-next@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>, <torvalds@...ux-foundation.org>
Subject: Re: What is the right practice to get new code upstream( was Fwd:
[patch] a simple hardware detector for latency as well as throughput ver.
0.1.0)
On 14.06.12 12:04:56, Peter Zijlstra wrote:
For AMD there's only event 02Bh, which is SMIs Received. I'm not sure it
> has anything like the FREEZE or if the event is modifyable to count the
> cycles in SMI.
Peter, which use cases do you have in mind. Is it to root cause
latencies? Or just to see what happens on the system, you long it
spends in smi mode? On current systems counting smi cycles seems not
to be possible.
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
--
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