linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mikhail Kshevetskiy" <mikhail.kshevetskiy@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, "Thomas Gleixner" <tglx@linutronix.de>
Subject: Fwd: x86_64 and AMD with C1E
Date: Mon, 1 Oct 2007 16:50:24 +0400	[thread overview]
Message-ID: <b70f2f960710010550i30ae48bu31f137fe46d70611@mail.gmail.com> (raw)
In-Reply-To: <b70f2f960710010546k4658aa1ay466f243ac707c989@mail.gmail.com>

01 Oct 2007 11:33:48 +0200, Andi Kleen <andi@firstfloor.org>:
>  Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com> writes:
> >
> > The same situation can be observed for linux-2.6.22.
>
> You're saying 2.6.22/x86-64 without any patches doesn't boot out of the box
> with C1E enabled? If yes what are the exact symptoms?
>
> -Andi
>

No, it boot and work normally. The only thing i bother, is the
additional 260 timer interrupts per seconds.
Here is short result:

c1e enabled:
  -- power consumption about 23 watts
  -- there is only C1 power state enabled
  -- there are about 260 timer interrupts per seconds
tested with  x86_64(2.6.22, 2.6.23-rc8, 2.6.23-rc8-hrt1 ),
i386(2.6.21, 2.6.22, 2.6.23-rc5-hrt1)

c1e disabled:
  -- power consumption about 27 watts
  -- there are no any power state enabled (including C1)
  -- there are no additional 260 timer interrupts per seconds
tested with 2.6.23-rc6-hrt1/x86_64.

I want to reduce the power consumption of my notebook. I see the 2 possibility:
  -- remove 260 additional timer interrupts (c1e enabled case )
  -- force enable C1, C2 and C3 states  (c1e disabled case)
Do you have any idea how it can be reached?


Mikhail Kshevetskiy

  parent reply	other threads:[~2007-10-01 12:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01  6:15 x86_64 and AMD with C1E Mikhail Kshevetskiy
2007-10-01  9:33 ` Andi Kleen
     [not found]   ` <b70f2f960710010546k4658aa1ay466f243ac707c989@mail.gmail.com>
2007-10-01 12:50     ` Mikhail Kshevetskiy [this message]
2007-10-01 14:14       ` Fwd: " Thomas Gleixner
2007-10-01 14:32         ` Andi Kleen
2007-10-01 14:59           ` Thomas Gleixner
2007-10-01 15:21             ` Andi Kleen
2007-10-01 16:44               ` Thomas Gleixner
2007-10-01 17:56               ` Chuck Ebbert
2007-10-01 14:33         ` Mikhail Kshevetskiy
2007-10-01 13:09     ` Andi Kleen
2007-10-01 14:06       ` Arjan van de Ven
2007-10-01 14:40       ` Mikhail Kshevetskiy
2007-10-19 16:39 ` Chuck Ebbert
2007-10-24 21:26   ` Mikhail Kshevetskiy
2007-10-24 21:41     ` Chuck Ebbert
2007-10-24 22:12       ` Thomas Gleixner
2007-10-24 22:42       ` Mikhail Kshevetskiy
2007-12-15 11:06       ` Thomas Gleixner

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=b70f2f960710010550i30ae48bu31f137fe46d70611@mail.gmail.com \
    --to=mikhail.kshevetskiy@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).