From: Jon Masters <jonathan@jonmasters.org>
To: Sven-Thorsten Dietrich <sdietrich@novell.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Lee Revell <rlrevell@joe-job.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: Sun, 25 Jan 2009 16:38:37 -0500 [thread overview]
Message-ID: <1232919517.1326.7.camel@jcmlaptop> (raw)
In-Reply-To: <1232849565.29318.112.camel@sven.thebigcorporation.com>
On Sun, 2009-01-25 at 13:12 +1100, Sven-Thorsten Dietrich wrote:
> I envision documentation of these specs, in a similar fashion to the
> manner in which CPU clock-cycles are documented for specific instruction
> executions - for those systems eligible (certified?) for low-latency
> operation.
I'd love to see a generic API that OS's could use to interface with
BIOS-level SMI implementations. Something provided in ACPI data. For all
I know, there already is something generic, but I've not heard of it?
It'd be really nice to have generic functions like:
disable_random_vendor_extensions_crap()
disable_all_non_essential_smis()
or whatever else.
> Providing benchmarking tools is definitely an excellent step in that
> direction (imo) - thanks.
Yeah. The more of this stuff, the better I think. So if someone wants to
help me polish what I posted then cool - it's in our "MRG" internal tree
already in the current form since we're only using it for debugging now.
Jon.
next prev parent reply other threads:[~2009-01-25 21:38 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 [this message]
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
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=1232919517.1326.7.camel@jcmlaptop \
--to=jonathan@jonmasters.org \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=sdietrich@novell.com \
--cc=tglx@linutronix.de \
--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