From: Lee Revell <rlrevell@joe-job.com>
To: Jon Masters <jcm@redhat.com>
Cc: Mike Kravetz <kravetz@us.ibm.com>,
linux-rt-users@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
williams <williams@redhat.com>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Subject: Re: [RT] [RFC] simple SMI detector
Date: Mon, 26 Jan 2009 21:23:45 -0500 [thread overview]
Message-ID: <75b66ecd0901261823o72339347kfa70d6e54f61af00@mail.gmail.com> (raw)
In-Reply-To: <1232992272.19862.3.camel@londonpacket.bos.redhat.com>
On Mon, Jan 26, 2009 at 12:51 PM, Jon Masters <jcm@redhat.com> wrote:
> On Sun, 2009-01-25 at 14:52 -0800, Mike Kravetz wrote:
>
>> Any reason why you could not do SMI detection in user level code running
>> at the highest RT priority?
>
> Yeah. I had some suggestions about that already...the problem with that
> is that you can't know whether measured latencies are due to SMIs /or/
> other kernel latencies - maybe there's a bug or other problem? I really
> want to be able to say to vendors "nope, it's definitely your problem".
Can't you do this with a known good version of the -rt kernel and the
latency tracer in full RT preempt mode? SMI induced latency will show
up in the trace as long delays in random code paths where kernel
induced latency can be ruled out.
Lee
next prev parent reply other threads:[~2009-01-27 2:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 22:55 [RT] [RFC] simple SMI detector Jon Masters
2009-01-24 2:33 ` Lee Revell
2009-01-24 16:30 ` Thomas Gleixner
2009-01-25 0:57 ` Jon Masters
2009-01-25 2:12 ` Sven-Thorsten Dietrich
2009-01-25 4:02 ` Theodore Tso
2009-01-25 9:40 ` Thomas Gleixner
2009-01-25 11:49 ` Bastien ROUCARIES
2009-01-25 15:04 ` Clark Williams
2009-01-25 21:41 ` Jon Masters
2009-01-25 21:38 ` Jon Masters
2009-01-25 9:34 ` Thomas Gleixner
2009-01-25 14:07 ` Henrique de Moraes Holschuh
2009-01-25 22:52 ` Mike Kravetz
2009-01-26 17:51 ` Jon Masters
2009-01-27 2:23 ` Lee Revell [this message]
2009-01-27 2:48 ` Keith Mannthey
2009-01-27 11:22 ` Pavel Machek
2009-01-27 15:17 ` Jon Masters
2009-01-27 18:00 ` Len Brown
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=75b66ecd0901261823o72339347kfa70d6e54f61af00@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=jcm@redhat.com \
--cc=kravetz@us.ibm.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.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