From: "H. Peter Anvin" <hpa@zytor.com>
To: Andreas Herrmann <herrmann.der.user@googlemail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] x86, amd: Make check_c1e_idle explicit
Date: Thu, 10 Dec 2009 17:03:43 -0800 [thread overview]
Message-ID: <4B219A6F.1060801@zytor.com> (raw)
In-Reply-To: <20091210133232.GA5471@alberich.amd.com>
This patch needs a lot better documentation. For one thing, it needs an
explicit patch comment!
In particular, is this a contract that fam 0x12+ will behave differently?
-hpa
On 12/10/2009 05:32 AM, Andreas Herrmann wrote:
>
> CC: stable@kernel.org
> Signed-off-by: Andreas Herrmann <andreas.herrmann3@amd.com>
> ---
> arch/x86/kernel/process.c | 14 ++++++--------
> 1 files changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
> index ea54ce8..1bf98b1 100644
> --- a/arch/x86/kernel/process.c
> +++ b/arch/x86/kernel/process.c
> @@ -494,21 +494,19 @@ static int __cpuinit mwait_usable(const struct cpuinfo_x86 *c)
> }
>
> /*
> - * Check for AMD CPUs, which have potentially C1E support
> + * Check for AMD CPUs, which potentially use SMI or hardware initiated C1E
> */
> static int __cpuinit check_c1e_idle(const struct cpuinfo_x86 *c)
> {
> if (c->x86_vendor != X86_VENDOR_AMD)
> return 0;
>
> - if (c->x86 < 0x0F)
> - return 0;
> -
> - /* Family 0x0f models < rev F do not have C1E */
> - if (c->x86 == 0x0f && c->x86_model < 0x40)
> - return 0;
> + if ((c->x86 == 0x0F && c->x86_model >= 0x40) ||
> + (c->x86 == 0x10) ||
> + (c->x86 == 0x11))
> + return 1;
>
> - return 1;
> + return 0;
> }
>
> static cpumask_var_t c1e_mask;
next prev parent reply other threads:[~2009-12-11 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 13:32 [PATCH] x86, amd: Make check_c1e_idle explicit Andreas Herrmann
2009-12-11 1:03 ` H. Peter Anvin [this message]
2009-12-11 13:23 ` [PATCH v2] " Andreas Herrmann
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=4B219A6F.1060801@zytor.com \
--to=hpa@zytor.com \
--cc=herrmann.der.user@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@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