From: Andi Kleen <andi@firstfloor.org>
To: Eduard-Gabriel Munteanu <eduard.munteanu@linux360.ro>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Option to disable AMD C1E (allows dynticks to work)
Date: Thu, 13 Dec 2007 23:33:07 +0100 [thread overview]
Message-ID: <p737ijigr8c.fsf@bingen.suse.de> (raw)
In-Reply-To: <20071214004442.5f9eba88@linux360.ro> (Eduard-Gabriel Munteanu's message of "Fri\, 14 Dec 2007 00\:44\:42 +0200")
Eduard-Gabriel Munteanu <eduard.munteanu@linux360.ro> writes:
>
> + force_amd_c1e [KNL,SMP,HW,BUGS=X86-64]
> + Don't disable C1E on AMD systems even if this means
The description/option is not correct. The mainline kernel never disables C1e.
Some distribution kernels and Xen do, perhaps you're confusing this
with them.
You would rather need a "force_disable_c1e" option if anything.
Anyways this should be near all obsolete with forced HPET. With HPET
dynticks can be used even with C1e. So in most cases you can just
use hpet=force instead and get dynticks and C1e together.
-Andi
next prev parent reply other threads:[~2007-12-13 22:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 22:44 [PATCH] Option to disable AMD C1E (allows dynticks to work) Eduard-Gabriel Munteanu
2007-12-13 22:33 ` Andi Kleen [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-12-13 22:47 Eduard-Gabriel Munteanu
2007-12-13 22:58 ` Johannes Weiner
2007-12-14 12:48 ` Eduard-Gabriel Munteanu
2007-12-18 15:43 ` Pavel Machek
2007-12-18 17:11 ` Eduard-Gabriel Munteanu
2007-12-14 0:14 Mikhail Kshevetskiy
[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-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
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=p737ijigr8c.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=eduard.munteanu@linux360.ro \
--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