public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] ACPI patches for 2.6.22 - part 2
Date: Thu, 10 May 2007 18:56:10 -0400	[thread overview]
Message-ID: <200705101856.11048.lenb@kernel.org> (raw)
In-Reply-To: <alpine.LFD.0.98.0705101353370.3986@woody.linux-foundation.org>

On Thursday 10 May 2007 16:56, Linus Torvalds wrote:
> 
> On Thu, 10 May 2007, Linus Torvalds wrote:
> > 
> > Seems to work for me. My evo correctly started the fan, and stopped it 
> > when the temperature went down again.
> 
> Looking at things in "top", I do end up occasionally seeing spikes where 
> kacpid takes 17% of CPU time, and kacpi_notify takes a few percent too. 
> But the machine works ok, and it doesn't seem to be horrible:
> 
>    64 ?        S<     0:15 [kacpid]
>    65 ?        S<     0:08 [kacpi_notify]
> 
> so they've gotten 23 seconds of CPU time over the 37 minutes that laptop 
> has been up now. That's arguably too much, but on the other hand, I did 
> end up trying to stress it out by doing some 3D stuff while compiling the 
> kernel and doing "git grep" over the kernel tree etc.

Thanks, I noticed the same thing on an nx6325.
The goal at the moment is to revert to the simplest functional & stable solution --
as what is shipping today crashes on some boxes.

We've got a couple of tweaks in mind where we think Linux can get
smarter -- but this is an area where several platform vendors are taking
advantage of Windows' implementation in (different) twisted ways.
For us to reach our goal of Linux handling any system out there
in as optimal a way as possible, we need to study each one in detail.

That said, can you send me or point me to the acpidump output
for your EVO.  Yes, I'm sure you've sent it before a long time
ago, but that was about probably 2,000,000 e-mail messages
and a couple of disk crashes ago:-)

thanks,
-Len

  reply	other threads:[~2007-05-10 22:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10  8:11 [GIT PATCH] ACPI patches for 2.6.22 - part 2 Len Brown
2007-05-10 20:31 ` Linus Torvalds
2007-05-10 20:56   ` Linus Torvalds
2007-05-10 22:56     ` Len Brown [this message]
2007-05-11  3:19       ` Linus Torvalds
2007-05-16 15:49 ` Ray Lee

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=200705101856.11048.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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