From: Eduard-Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: nihil13z@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Option to disable AMD C1E (allows dynticks to work)
Date: Mon, 17 Dec 2007 14:40:37 +0200 [thread overview]
Message-ID: <20071217144037.76553a92@linux360.ro> (raw)
In-Reply-To: <e238f7c8-6c0a-4734-a0f8-98687b61e714@s8g2000prg.googlegroups.com>
On Sun, 16 Dec 2007 06:29:57 -0800 (PST)
nihil13z@gmail.com wrote:
> On Dec 15, 2:20 am, Eduard-Gabriel Munteanu
> <eduard.munte...@linux360.ro> wrote:
> > On Fri, 14 Dec 2007 17:35:13 -0500
> >
> > But maybe someone with access to such hardware can tell us what
> > happens: does he get C2/C3 power states under such circumstances?
>
> Hi,
>
> I have a nx6325 laptop with Turion 64 X2 CPU. So far I have had no
> success
> in getting NO_HZ to work on my box.
>
> I am a C coder, but have no experience in kernel hacking. However, I
> _really_ would
> like to help resolve this issue.
>
> It would be nice if You could give me any information on what/where to
> look for. Also,
> I would be happy to test any patches for this specific problem.
>
> Thanks,
> Cubris Zukilla, nihil13z@gmail.com
Hi,
The patch I submitted gets NOHZ working, but it doesn't improve power
savings. The power usage actually increases by 1 watt or so on my
laptop, because there are no other C-states higher than C1 available
and C1E needs to be disabled.
I wasn't asking for testers for this patch. Instead, my question was
related to those laptops that disable C1E on the first CPU, but not on
the second. Does the BIOS offer an option to disable C1E? Does the BIOS
fill higher C-states? Andi Kleen provided an answer to my question,
saying that AMD doesn't currently support higher C-states on multi-core
CPUs, but I was wondering whether this was an attempt on the laptop
vendor's part to provide this functionality or just an ugly bug.
There isn't much you could do. The problem is rooted quite deeply
inside Linux and I don't think this would be a beginner's task.
Moreover, there are lots of hardware quirks one must account for.
parent reply other threads:[~2007-12-17 12:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <e238f7c8-6c0a-4734-a0f8-98687b61e714@s8g2000prg.googlegroups.com>]
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=20071217144037.76553a92@linux360.ro \
--to=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=nihil13z@gmail.com \
/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