From: Robert Richter <robert.richter@amd.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Luming Yu <luming.yu@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, <tglx@linutronix.de>,
<sfr@canb.auug.org.au>, Andrew Morton <akpm@linux-foundation.org>,
<jcm@jonmasters.org>, <linux-next@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, <torvalds@linux-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)
Date: Thu, 21 Jun 2012 15:29:14 +0200 [thread overview]
Message-ID: <20120621132914.GA24632@erda.amd.com> (raw)
In-Reply-To: <1339668296.2559.25.camel@twins>
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
next prev parent reply other threads:[~2012-06-21 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 12:57 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) Luming Yu
2012-06-12 14:42 ` Jimmy Thrasibule
2012-06-12 14:57 ` Luming Yu
2012-06-13 22:20 ` Andrew Morton
2012-06-14 9:25 ` Luming Yu
2012-06-14 10:04 ` Peter Zijlstra
2012-06-14 14:15 ` Luming Yu
2012-06-21 13:29 ` Robert Richter [this message]
2012-06-21 14:43 ` Peter Zijlstra
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=20120621132914.GA24632@erda.amd.com \
--to=robert.richter@amd.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=jcm@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luming.yu@gmail.com \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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