From: Eduard-Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: Johannes Weiner <hannes-kernel@saeurebad.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Option to disable AMD C1E (allows dynticks to work)
Date: Fri, 14 Dec 2007 14:48:41 +0200 [thread overview]
Message-ID: <20071214144841.2e4e4992@linux360.ro> (raw)
In-Reply-To: <x77ijiryl1.fsf@saeurebad.de>
On Thu, 13 Dec 2007 23:58:50 +0100
Johannes Weiner <hannes-kernel@saeurebad.de> wrote:
> I would find this way more readable:
>
> if (lo & ENABLE_C1E_MASK) {
> #ifdef CONFIG_X86_AMD_C1E_WORKAROUND
> if (disable_amd_c1e) {
> ...
> #else
> return 1;
> #endif
> }
I wanted to avoid using too many tabs, as that would require the lines
inside the if block to be split too many times. I'll resubmit the patch
if you think it's necessary.
> Why does it require to be enabled by compile-time AND run-time? Is
> that something you might want to decide on every boot? Could we make
> it settable at boot-time xor at compile-time?
Making it settable only at boot-time means compiling in unnecessary
code. Also, making it settable only at compile-time would be bad for
distros that distribute binary kernels, as some users may experience
worse power savings with dynticks than with C1E (especially when C2, C3
and higher C-states are not available, due to brain-dead firmware).
This allows them to opt for leaving C1E enabled.
It is not required to enable it at both compile-time and boot-time. You
enable it at compile-time and then you _can disable_ it at boot-time.
next prev parent reply other threads:[~2007-12-14 9:52 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 22:47 [PATCH] Option to disable AMD C1E (allows dynticks to work) Eduard-Gabriel Munteanu
2007-12-13 22:58 ` Johannes Weiner
2007-12-14 12:48 ` Eduard-Gabriel Munteanu [this message]
2007-12-18 15:43 ` Pavel Machek
2007-12-18 17:11 ` Eduard-Gabriel Munteanu
-- strict thread matches above, loose matches on Subject: below --
2007-12-29 14:43 David P. Reed
2007-12-29 22:28 ` Islam Amer
2007-12-30 0:35 ` Islam Amer
2007-12-30 12:57 ` Ingo Molnar
2007-12-30 1:38 ` Rene Herman
2007-12-30 1:49 ` Islam Amer
2007-12-30 3:24 ` Rene Herman
2007-12-30 10:17 ` Eduard-Gabriel Munteanu
2007-12-30 14:42 ` Andi Kleen
2007-12-30 21:12 ` Eduard-Gabriel Munteanu
2007-12-31 2:34 ` Andi Kleen
2007-12-30 20:57 ` Richard Harman
2007-12-30 21:18 ` Eduard-Gabriel Munteanu
2007-12-30 13:36 ` Richard Harman
2007-12-30 23:32 ` Eduard-Gabriel Munteanu
2007-12-31 0:30 ` David P. Reed
[not found] <47754735.1050009@richardharman.com>
2007-12-29 7:52 ` Eduard-Gabriel Munteanu
2007-12-29 9:09 ` Richard Harman
2007-12-29 11:19 ` Eduard-Gabriel Munteanu
2007-12-29 11:46 ` Islam Amer
2007-12-30 20:45 ` Rene Herman
2007-12-14 0:14 Mikhail Kshevetskiy
2007-12-13 22:44 Eduard-Gabriel Munteanu
2007-12-13 22:33 ` Andi Kleen
2007-12-14 12:39 ` Eduard-Gabriel Munteanu
2007-12-14 10:17 ` Andi Kleen
2007-12-14 13:41 ` Eduard-Gabriel Munteanu
2007-12-14 12:20 ` Andi Kleen
2007-12-14 16:01 ` Eduard-Gabriel Munteanu
2007-12-14 18:07 ` Thomas Gleixner
2007-12-14 18:12 ` Andi Kleen
2007-12-14 19:57 ` Thomas Gleixner
2007-12-14 20:06 ` Andi Kleen
2007-12-14 19:58 ` Eduard-Gabriel Munteanu
2007-12-14 18:10 ` Andi Kleen
2007-12-14 19:53 ` Thomas Gleixner
2007-12-14 22:35 ` Chuck Ebbert
2007-12-15 0:10 ` Eduard-Gabriel Munteanu
2007-12-15 12:41 ` Andi Kleen
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=20071214144841.2e4e4992@linux360.ro \
--to=eduard.munteanu@linux360.ro \
--cc=hannes-kernel@saeurebad.de \
--cc=linux-kernel@vger.kernel.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