lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b70f2f960710010733m6932c0b3raa35d59b393538fd@mail.gmail.com>
Date:	Mon, 1 Oct 2007 18:33:40 +0400
From:	"Mikhail Kshevetskiy" <mikhail.kshevetskiy@...il.com>
To:	"Thomas Gleixner" <tglx@...utronix.de>
Cc:	"Andi Kleen" <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: Fwd: x86_64 and AMD with C1E

2007/10/1, Thomas Gleixner <tglx@...utronix.de>:
> On Mon, 1 Oct 2007, Mikhail Kshevetskiy wrote:
> > 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 )
>
> There is work in progress on a patch, which allows to utilize the hpet
> timers as per cpu timers. This should solve the problem. Be patient.

I can test it on i386/x86_64 architectures.

Mikhail Kshevetskiy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ