public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
To: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
Cc: Dino Klein <dinoklein-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Entering C3 Processor State without a Bus Arbiter
Date: Fri, 16 Jan 2004 10:30:55 +0100	[thread overview]
Message-ID: <20040116093055.GE9814@dominikbrodowski.de> (raw)
In-Reply-To: <20040115154555.V73140-Y6VGUYTwhu0@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]

On Thu, Jan 15, 2004 at 03:52:12PM -0800, Nate Lawson wrote:
> > After removing the restrictions in the source files, and adding a WBINVD
> > instruction right before the read from P_LVL3 - the processor was put in
> > the C3 state. This is on my Via Apollo Pro133A based Abit VP6 board,
> > which does not have a Bus Arbiter. Just for the record, I did pull out
> > the second CPU, so I can do "safer" experimentation.
> 
> WBINVD is too expensive when you're entering C3 hundreds of times per
> second.  Try playing back an mp3 while dd'ing a CDROM in PIO mode to your
> hard drive.  Goodbye data, hello backups!  The CPU can't snoop the bus in
> C3.

You shouldn't enter C3 at all when the CPU is woken up hundreds of times per
second. Maximum allowed latency is 1ms, IIRC -- you really shouldn't get
into this state while dd'ing a CDROM or something else...

Problem is, WBINVD might take even longer than 1ms, even though the maximum
I got on my PIII notebook was about 900us...

	Dominik

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-01-16  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-15 22:29 Entering C3 Processor State without a Bus Arbiter Dino Klein
     [not found] ` <Law11-OE36TK4GXSNMh0000bd93-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
2004-01-15 23:25   ` Dominik Brodowski
2004-01-15 23:52   ` Nate Lawson
     [not found]     ` <20040115154555.V73140-Y6VGUYTwhu0@public.gmane.org>
2004-01-16  9:30       ` Dominik Brodowski [this message]
     [not found]         ` <20040116093055.GE9814-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-01-16 17:33           ` Nate Lawson
     [not found]             ` <20040116092917.W76365-Y6VGUYTwhu0@public.gmane.org>
2004-01-16 18:02               ` Dominik Brodowski
     [not found]                 ` <20040116180225.GB5090-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-01-18  3:00                   ` Ducrot Bruno
2004-01-17 18:11             ` Dino Klein
  -- strict thread matches above, loose matches on Subject: below --
2004-01-18  7:14 Yu, Luming

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=20040116093055.GE9814@dominikbrodowski.de \
    --to=linux-x3ehhduj6siigcdfoqap7bvvk+yq3zxh@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=dinoklein-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org \
    --cc=nate-Y6VGUYTwhu0@public.gmane.org \
    /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