From: Jon Masters <jcm@redhat.com>
To: Luming Yu <luming.yu@gmail.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
Jon Masters <jonathan@jonmasters.org>
Subject: Re: [PATCH update 0/3] HW-latency: hardware latency test 0.10
Date: Sun, 11 Nov 2012 23:13:28 -0500 [thread overview]
Message-ID: <50A07768.5010704@redhat.com> (raw)
In-Reply-To: <1352602102-2390-1-git-send-email-luming.yu@gmail.com>
On 11/10/2012 09:48 PM, Luming Yu wrote:
> Update the previous patch series to ACK all comments I've recevied so far
> for the tool: e.g. 1.Acked Jon Masters in source code as many code are from
> jcm, thanks very much Jon. 2. squashed all changes against new file I added into
> one. 3. Make it useful on non-x86.
Thanks for taking this and doing the heavy lifting to get it upstream! I
wrote the original SMI detector really for RT debug purposes as we had
OEM systems that would generate large latencies and it was easier to
prove the point with nice graphs showing where the BIOS was injecting
unwanted SMIs. Glad to see the work being done to make it more generic
in nature. Maybe I'll come back with some ARM patches ;)
Actually this exercise was very informative because it has helped shape
my input on ARMv8 designs. I'm very keen to get away from a world in
which world+dog feature is implemented inside an SMI-like context. It
should be done via a dedicated management processor (on-chip) instead.
Jon.
next prev parent reply other threads:[~2012-11-12 4:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 2:48 [PATCH update 0/3] HW-latency: hardware latency test 0.10 Luming Yu
2012-11-11 2:48 ` [PATCH update 1/3] " Luming Yu
2012-11-11 2:48 ` [PATCH update 2/3] x86: Delete too many "Fast TSC .." in dmesg from HW_latency cyclic sampling Luming Yu
2012-11-11 2:48 ` [PATCH update 3/3] fs: Fix crash caused by write to dummy debugfs interface like HW_latency exposed Luming Yu
2012-11-11 8:23 ` [PATCH update 0/3] HW-latency: hardware latency test 0.10 Chen Gong
2012-11-12 4:13 ` Jon Masters [this message]
2012-11-18 9:30 ` Luming Yu
2012-11-19 7:30 ` Jon Masters
2012-11-27 2:43 ` Luming Yu
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=50A07768.5010704@redhat.com \
--to=jcm@redhat.com \
--cc=arnd@arndb.de \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).