From patchwork Sun Oct 11 18:28:19 2009 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [Fwd:,Re:,[PATCH] x86: Relegate CONFIG_PAT to EMBEDDED] From: Tim Gardner X-Patchwork-Id: 35717 Message-Id: <4AD223C3.3020607@canonical.com> To: Andy Whitcroft , Stefan Bader Cc: Kernel team list Date: Sun, 11 Oct 2009 12:28:19 -0600 Andy, Stefan - Why _is_ it that we don't have PAT enabled? Wasn't it originally a prerequisite for KMS back in Jaunty days? There are some comments on LKML pointing out that we _should_ have PAT enabled, e.g., "[RFC Patch] use MTRR for write combining if PAT is not available" rtg diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 4427956..2fbc3c6 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -1327,7 +1327,9 @@ config MATH_EMULATION kernel, it won't hurt. config MTRR - bool "MTRR (Memory Type Range Register) support" + bool + default y + prompt "MTRR (Memory Type Range Register) support" if EMBEDDED ---help--- On Intel P6 family processors (Pentium Pro, Pentium II and later) the Memory Type Range Registers (MTRRs) may be used to control @@ -1393,7 +1395,8 @@ config MTRR_SANITIZER_SPARE_REG_NR_DEFAULT config X86_PAT bool - prompt "x86 PAT support" + default y + prompt "x86 PAT support" if EMBEDDED depends on MTRR ---help--- Use PAT attributes to setup page level cache control.