From: Lee Revell <rlrevell@joe-job.com>
To: Andi Kleen <ak@suse.de>
Cc: Tim Hockin <thockin@hockin.org>,
Erick Turnquist <jhujhiti@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Lost Ticks on x86_64
Date: Mon, 08 Aug 2005 14:09:58 -0400 [thread overview]
Message-ID: <1123524598.15269.29.camel@mindpipe> (raw)
In-Reply-To: <20050808120125.GD19170@wotan.suse.de>
On Mon, 2005-08-08 at 14:01 +0200, Andi Kleen wrote:
> > Some BIOSes do not lock SMM, and you *could* turn it off at the chipset
> > level.
>
> Doing so would be wasteful though. Both AMD and Intel CPUs need SMM code
> for the deeper C* sleep states.
>
Wouldn't it be useful for !CONFIG_PM? Many multimedia users run this
way because they want their machines running full speed all the time
(they need the horsepower, plus frequency scaling interferes with the
TSC based timing used by JACK ) and because ACPI has a history of
causing nasty latency blips.
Lee
next prev parent reply other threads:[~2005-08-08 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5348b8ba050806204453392f7f@mail.gmail.com.suse.lists.linux.kernel>
2005-08-07 11:36 ` Lost Ticks on x86_64 Andi Kleen
2005-08-07 17:07 ` Erick Turnquist
2005-08-07 17:48 ` Tim Hockin
2005-08-07 18:46 ` Erick Turnquist
2005-08-07 20:14 ` Tim Hockin
2005-08-08 12:01 ` Andi Kleen
2005-08-08 16:47 ` Tim Hockin
2005-08-08 16:51 ` Andi Kleen
2005-08-08 18:09 ` Lee Revell [this message]
2005-08-07 18:51 ` Lee Revell
2005-08-07 20:04 ` Zwane Mwaikambo
2005-08-07 21:24 ` Tim Hockin
2005-08-07 14:29 Parag Warudkar
2005-08-07 16:19 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-08-07 3:44 Erick Turnquist
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=1123524598.15269.29.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=ak@suse.de \
--cc=jhujhiti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@hockin.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