From: "Allen Martin" <AMartin@nvidia.com>
To: "Jeff Garzik" <jeff@garzik.org>,
"Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Lee Revell" <rlrevell@joe-job.com>, "Andi Kleen" <ak@suse.de>,
"Jason Baron" <jbaron@redhat.com>, <linux-kernel@vger.kernel.org>,
"john stultz" <johnstul@us.ibm.com>
Subject: RE: libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer]
Date: Wed, 15 Mar 2006 16:33:39 -0800 [thread overview]
Message-ID: <DBFABB80F7FD3143A911F9E6CFD477B00E48CD06@hqemmail02.nvidia.com> (raw)
> >>well, it's a PIO inb() op i think, and could thus in theory
> trigger SMM
> >>BIOS code.
> >
> >
> > Is there any easy way to disable more SMM stuff than "noacpi"?
>
> It's unlikely you can disable SMM stuff even with noacpi...
>
There should be no SMI traps on ATA BARs. At least we don't put any in
our reference BIOS and I can't imagine why any of the BIOS vendors or
motherboard mfgs would add any.
-Allen
next reply other threads:[~2006-03-16 0:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 0:33 Allen Martin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-27 21:22 AMD64 X2 lost ticks on PM timer bubshait
2006-03-03 22:09 ` Jeff Garzik
2006-03-03 23:43 ` Bill Rugolsky Jr.
2006-03-04 0:07 ` Andi Kleen
[not found] ` <20060315213638.GA17817@ti64.telemetry-investments.com>
2006-03-15 21:45 ` libata/sata_nv latency on NVIDIA CK804 [was Re: AMD64 X2 lost ticks on PM timer] Lee Revell
2006-03-15 21:58 ` Ingo Molnar
2006-03-15 22:00 ` Ingo Molnar
2006-03-15 22:25 ` Jeff Garzik
2006-03-16 15:13 ` Alan Cox
2006-03-16 16:57 ` Bill Rugolsky Jr.
2006-03-22 16:09 ` Andi Kleen
2006-03-22 18:39 ` Bill Rugolsky Jr.
2006-03-22 23:07 ` Bill Rugolsky Jr.
2006-03-15 22:22 ` Jeff Garzik
2006-03-15 22:24 ` Ingo Molnar
2006-03-15 22:36 ` Bill Rugolsky Jr.
2006-03-15 22:46 ` Ingo Molnar
2006-03-15 22:48 ` Jeff Garzik
2006-03-15 23:31 ` Lee Revell
2006-03-15 21:50 ` Ingo Molnar
2006-03-15 22:11 ` Ingo Molnar
2006-03-15 22:33 ` Jeff Garzik
2006-03-15 22:44 ` Ingo Molnar
2006-03-15 22:50 ` Jeff Garzik
2006-03-15 23:14 ` Bill Rugolsky Jr.
2006-03-15 23:44 ` Lee Revell
2006-03-16 3:15 ` Bill Rugolsky Jr.
2006-03-16 4:20 ` Lee Revell
2006-03-16 9:18 ` Ingo Molnar
2006-03-16 14:42 ` Gabor Gombas
2006-03-16 0:01 ` Lee Revell
2006-03-16 0:14 ` Jeff Garzik
2006-03-15 22:30 ` Jeff Garzik
2006-03-15 22:36 ` Ingo Molnar
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=DBFABB80F7FD3143A911F9E6CFD477B00E48CD06@hqemmail02.nvidia.com \
--to=amartin@nvidia.com \
--cc=ak@suse.de \
--cc=brugolsky@telemetry-investments.com \
--cc=jbaron@redhat.com \
--cc=jeff@garzik.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rlrevell@joe-job.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).