From: Borislav Petkov <bp@alien8.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>, sherry.hurwitz@amd.com
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/cpu/AMD: Fix CPB bit for more processors
Date: Fri, 16 Nov 2018 10:54:24 +0100 [thread overview]
Message-ID: <20181116095424.GA20313@zn.tnic> (raw)
In-Reply-To: <20181116053106.11571-1-jiaxun.yang@flygoat.com>
On Fri, Nov 16, 2018 at 01:31:06PM +0800, Jiaxun Yang wrote:
> CPUID Fn8000_0007_EDX[CPB] is wrongly 0 on Model 17,
> Stepping 0, but revision guide has not been released for
> newer Family 17h models.
>
> Tesed on AMD "Ryzen 7 2700U with Radeon Vega Mobile Gfx"
> and "AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx",
> their CPUID Fn0000_0001_EAX is 0x00810f10 and should have
> CPB feature according AMD product specifications, however
> their Fn8000_0007_EDX is 0x00006599, indicating they don't
> support CPB feature.
>
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> ---
> arch/x86/kernel/cpu/amd.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
> index eeea634bee0a..7db43ef8e97e 100644
> --- a/arch/x86/kernel/cpu/amd.c
> +++ b/arch/x86/kernel/cpu/amd.c
> @@ -821,8 +821,12 @@ static void init_amd_zn(struct cpuinfo_x86 *c)
> /*
> * Fix erratum 1076: CPB feature bit not being set in CPUID. It affects
> * all up to and including B1.
> + *
> + * Revision guide for Family 17h, Model 17 has not been released, but
> + * Model 17, Stepping 0 have the same issue.
> */
> - if (c->x86_model <= 1 && c->x86_stepping <= 1)
> + if ((c->x86_model <= 1 && c->x86_stepping <= 1) || \
> + (c->x86_model == 17 && c->x86_stepping == 0))
> set_cpu_cap(c, X86_FEATURE_CPB);
> }
Actually, I'd prefer if we stopped doing all the checks and simply do
this:
if (!cpu_has(c, X86_FEATURE_CPB))
set_cpu_cap(c, X86_FEATURE_CPB);
for all F17h as it is a safe assumption that family 0x17 has CPB -
regardless of CPUID bit setting.
Sherry?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
prev parent reply other threads:[~2018-11-16 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 5:31 Jiaxun Yang
2018-11-16 9:54 ` Borislav Petkov [this message]
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=20181116095424.GA20313@zn.tnic \
--to=bp@alien8.de \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sherry.hurwitz@amd.com \
--cc=x86@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
all inboxes | Powered by JetHome®