From: Lee Revell <rlrevell@joe-job.com>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: george@mvista.com, john stultz <johnstul@us.ibm.com>,
Greg KH <greg@kroah.com>,
ganzinger@mvista.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Calibration issues with USB disc present.
Date: Wed, 16 Nov 2005 19:30:23 -0500 [thread overview]
Message-ID: <1132187423.3008.21.camel@mindpipe> (raw)
In-Reply-To: <437BC8D6.4040402@qualcomm.com>
On Wed, 2005-11-16 at 16:03 -0800, Max Krasnyansky wrote:
> I think in the short term your best bet is to globally disable SMI at
> early
> boot stage (ie before TSC calibration).
> Some people might argue that it's not the most graceful solution
> because it might
> brake some BIOS features but it's a very common trick that is used by
> RT folks
> (for example RTAI has configurable option to enable SMI workaround)
> because
> on some chipset/BIOS combinations SMIs introduce horrible latencies.
> And you
> cannot do much about that other than disabling SMI.
> I have not seen any reports of negative side effects of disabling SMI
> yet. But
> if you're worried about that you could re-enable it later when you're
> done with
> TSC calibration and stuff.
>
Hmm, interesting, I had no idea this was possible. Is there a generic
way to disable SMI? It would be useful for the -rt tree as lots of low
latency audio users have problems with SMI induced underruns.
Lee
next prev parent reply other threads:[~2005-11-17 0:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 21:37 Calibration issues with USB disc present George Anzinger
2005-11-11 21:57 ` john stultz
2005-11-12 5:05 ` Greg KH
2005-11-12 16:06 ` George Anzinger
2005-11-12 21:33 ` Greg KH
2005-11-14 18:56 ` George Anzinger
2005-11-14 18:49 ` Greg KH
2005-11-14 19:46 ` Brad Campbell
2005-11-14 19:43 ` Greg KH
2005-11-14 19:58 ` john stultz
2005-11-14 21:52 ` George Anzinger
2005-11-17 0:03 ` Max Krasnyansky
2005-11-17 0:30 ` Lee Revell [this message]
2005-11-17 17:43 ` Max Krasnyansky
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=1132187423.3008.21.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=ganzinger@mvista.com \
--cc=george@mvista.com \
--cc=greg@kroah.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.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