linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pu Wen <puwen@hygon.cn>
To: bp@alien8.de, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, x86@kernel.org, thomas.lendacky@amd.com
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	Pu Wen <puwen@hygon.cn>
Subject: [PATCH v7 03/16] x86/cpu/mtrr: Support TOP_MEM2 and get MTRR number
Date: Mon, 17 Sep 2018 21:29:53 +0800	[thread overview]
Message-ID: <8246f81648d014601de3812ade40e85d9c50d9b3.1537182523.git.puwen@hygon.cn> (raw)
In-Reply-To: <cover.1537182523.git.puwen@hygon.cn>

The Hygon Dhyana CPU has a special magic MSR way to force WB for
memory >4GB, and support TOP_MEM2. Therefore, it is necessary to
add Hygon Dhyana support in amd_special_default_mtrr().

The number of variable MTRRs for Hygon is 2 as AMD's.

Signed-off-by: Pu Wen <puwen@hygon.cn>
Reviewed-by: Borislav Petkov <bp@suse.de>
---
 arch/x86/kernel/cpu/mtrr/cleanup.c | 3 ++-
 arch/x86/kernel/cpu/mtrr/mtrr.c    | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/arch/x86/kernel/cpu/mtrr/cleanup.c b/arch/x86/kernel/cpu/mtrr/cleanup.c
index 765afd5..3668c5d 100644
--- a/arch/x86/kernel/cpu/mtrr/cleanup.c
+++ b/arch/x86/kernel/cpu/mtrr/cleanup.c
@@ -831,7 +831,8 @@ int __init amd_special_default_mtrr(void)
 {
 	u32 l, h;
 
-	if (boot_cpu_data.x86_vendor != X86_VENDOR_AMD)
+	if (boot_cpu_data.x86_vendor != X86_VENDOR_AMD &&
+	    boot_cpu_data.x86_vendor != X86_VENDOR_HYGON)
 		return 0;
 	if (boot_cpu_data.x86 < 0xf)
 		return 0;
diff --git a/arch/x86/kernel/cpu/mtrr/mtrr.c b/arch/x86/kernel/cpu/mtrr/mtrr.c
index 9a19c80..507039c 100644
--- a/arch/x86/kernel/cpu/mtrr/mtrr.c
+++ b/arch/x86/kernel/cpu/mtrr/mtrr.c
@@ -127,7 +127,7 @@ static void __init set_num_var_ranges(void)
 
 	if (use_intel())
 		rdmsr(MSR_MTRRcap, config, dummy);
-	else if (is_cpu(AMD))
+	else if (is_cpu(AMD) || is_cpu(HYGON))
 		config = 2;
 	else if (is_cpu(CYRIX) || is_cpu(CENTAUR))
 		config = 8;
-- 
2.7.4


  parent reply	other threads:[~2018-09-17 13:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 13:28 [PATCH v7 00/16] Add support for Hygon Dhyana Family 18h processor Pu Wen
2018-09-17 13:29 ` [PATCH v7 01/16] x86/cpu: Create Hygon Dhyana architecture support file Pu Wen
2018-09-17 13:29 ` [PATCH v7 02/16] x86/cpu: Get cache info and setup cache cpumap for Hygon Dhyana Pu Wen
2018-09-17 13:29 ` Pu Wen [this message]
2018-09-17 13:30 ` [PATCH v7 04/16] x86/smpboot: SMP init no delay and not flush caches before sleep Pu Wen
2018-09-17 13:30 ` [PATCH v7 05/16] perf/x86: Add Hygon Dhyana support to PMU infrastructure Pu Wen
2018-09-17 13:30 ` [PATCH v7 06/16] x86/alternative: Init ideal_nops for Hygon Dhyana Pu Wen
2018-09-17 13:30 ` [PATCH v7 07/16] x86/pci: Add Hygon Dhyana support to PCI and north bridge Pu Wen
2018-09-19  3:19   ` [LKP] [x86/pci] 7ffb31888c: PANIC:early_exception kernel test robot
2018-09-19 13:53     ` Pu Wen
2018-09-20  0:26       ` Rong Chen
2018-09-20  8:47         ` Pu Wen
2018-09-20  9:39           ` Thomas Gleixner
2018-09-23 10:05             ` Pu Wen
2018-09-17 13:31 ` [PATCH v7 08/16] x86/apic: Add Hygon Dhyana support to APIC Pu Wen
2018-09-17 13:31 ` [PATCH v7 09/16] x86/bugs: Add mitigation to spectre and no meltdown for Hygon Dhyana Pu Wen
2018-09-17 13:32 ` [PATCH v7 10/16] x86/mce: Add Hygon Dhyana support to MCE infrastructure Pu Wen
2018-09-17 13:32 ` [PATCH v7 11/16] x86/kvm: Add Hygon Dhyana support to KVM infrastructure Pu Wen
2018-09-17 13:42   ` Pu Wen
2018-09-17 13:33 ` [PATCH v7 12/16] x86/xen: Add Hygon Dhyana support to Xen Pu Wen
2018-09-17 13:33 ` [PATCH v7 13/16] ACPI, x86: Add Hygon Dhyana support Pu Wen
2018-09-17 13:33 ` [PATCH v7 14/16] cpufreq, " Pu Wen
2018-09-17 13:34 ` [PATCH v7 15/16] EDAC, amd64: " Pu Wen
2018-09-17 13:35 ` [PATCH v7 16/16] cpupower, x86: " Pu Wen

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=8246f81648d014601de3812ade40e85d9c50d9b3.1537182523.git.puwen@hygon.cn \
    --to=puwen@hygon.cn \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@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;
as well as URLs for NNTP newsgroup(s).