From: Lee Revell <rlrevell@joe-job.com>
To: "Sébastien Dugué" <sebastien.dugue@bull.net>
Cc: john stultz <johnstul@us.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: preempt-rt, NUMA and strange latency traces
Date: Fri, 10 Feb 2006 14:07:54 -0500 [thread overview]
Message-ID: <1139598475.19342.8.camel@mindpipe> (raw)
In-Reply-To: <1139576865.5706.68.camel@frecb000686>
On Fri, 2006-02-10 at 14:07 +0100, Sébastien Dugué wrote:
> That's the problem and I'll have to synchronize for a proper window
> for running my tests.
>
> Is this SMI thing IBM's eyes only stuff or is it documented
> somewhere?
>
No, I wish it was just IBM. Lots of modern systems unfortunately use
SMM (system management mode, which is entered when we get a system
management interrupts) to implement all kinds of PM and BIOS junk and
various value added features.
Most of these systems are laptops and are utterly unusable for low
latency work. Worse, most of this stuff is considered highly
proprietary by the vendors (probably because it leands to such suckage).
Lee
next prev parent reply other threads:[~2006-02-10 19:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 11:28 preempt-rt, NUMA and strange latency traces Sébastien Dugué
2006-02-08 9:41 ` Steven Rostedt
2006-02-08 10:25 ` Ingo Molnar
2006-02-08 10:47 ` Sébastien Dugué
2006-02-08 10:45 ` Sébastien Dugué
2006-02-08 16:49 ` john stultz
2006-02-09 11:11 ` Sébastien Dugué
2006-02-09 11:26 ` Sébastien Dugué
2006-02-09 18:54 ` john stultz
2006-02-10 13:07 ` Sébastien Dugué
2006-02-10 19:07 ` Lee Revell [this message]
2006-02-09 6:04 ` Lee Revell
2006-02-09 11:24 ` Sébastien Dugué
2006-02-09 20:02 ` Lee Revell
2006-02-10 13:18 ` Sébastien Dugué
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=1139598475.19342.8.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=sebastien.dugue@bull.net \
/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