public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Jonathan Lundell <linux@lundell-bros.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: RE: x86 TSC time warp puzzle
Date: Sat, 02 Apr 2005 03:13:36 -0500	[thread overview]
Message-ID: <1112429616.24111.7.camel@mindpipe> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6004629635@scsmsx403.amr.corp.intel.com>

On Fri, 2005-04-01 at 23:05 -0800, Pallipadi, Venkatesh wrote:
> It can be SMI happening in the platform. Typically BIOS uses some SMI
> polling 
> to handle some devices during early boot. Though 500 microseconds sounds
> a 
> bit too high.
> 

Nope, that sounds just about right.  Buggy BIOSes that implement ACPI
via SMM (or so I have been told) can stall the machine for over a
millisecond, this is why some laptops lose timer ticks at HZ=1000.  The
issue is well known by Linux audio users, as it causes big problems for
people who buy laptops for live audio use.

A list of known good/bad machines would be a tremendous help, but no one
knows the exact extent of the problem.  All Acer laptops seem to be
affected.

Hardware manufacturers (laptops anyway) don't seem to care about
anything below 1-2ms because Windows uses HZ=100 and the ASIO drivers on
that platform only go down to about ~1.5 ms latency.

Lee




  reply	other threads:[~2005-04-02  8:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-02  7:05 x86 TSC time warp puzzle Pallipadi, Venkatesh
2005-04-02  8:13 ` Lee Revell [this message]
2005-04-03  4:04   ` Jonathan Lundell
  -- strict thread matches above, loose matches on Subject: below --
2005-04-02  1:43 Jonathan Lundell
2005-04-04  8:59 ` P
2005-04-04 13:58   ` Joe Korty

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=1112429616.24111.7.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@lundell-bros.com \
    --cc=venkatesh.pallipadi@intel.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