Re: [tip:x86/smap] x86-32: Start out eflags and cr4 clean

2012-11-23 Thread H. Peter Anvin

On 11/23/2012 07:49 PM, Yuhong Bao wrote:

+ * Specifically, cr4 exists if and only if CPUID exists,
+ * which in turn exists if and only if EFLAGS.ID exists.

This may be true for *Intel* 486 CPUs as VME was implemented at the same time 
as CPUID, but I am not sure that it is true for AMD 486 CPUs.

Yuhong Bao  


That is the architecture; if you know of a counterexample speak up.  "I 
am not sure" doesn't count.


-hpa

--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


RE: [tip:x86/smap] x86-32: Start out eflags and cr4 clean

2012-11-23 Thread Yuhong Bao
> + * Specifically, cr4 exists if and only if CPUID exists,
> + * which in turn exists if and only if EFLAGS.ID exists.
This may be true for *Intel* 486 CPUs as VME was implemented at the same time 
as CPUID, but I am not sure that it is true for AMD 486 CPUs.

Yuhong Bao--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[tip:x86/smap] x86-32: Start out eflags and cr4 clean

2012-09-26 Thread tip-bot for H. Peter Anvin
Commit-ID:  5a5a51db78ef24aa61a4cb2ae36f07f6fa37356d
Gitweb: http://git.kernel.org/tip/5a5a51db78ef24aa61a4cb2ae36f07f6fa37356d
Author: H. Peter Anvin 
AuthorDate: Mon, 24 Sep 2012 16:05:48 -0700
Committer:  H. Peter Anvin 
CommitDate: Wed, 26 Sep 2012 15:06:22 -0700

x86-32: Start out eflags and cr4 clean

%cr4 is supposed to reflect a set of features into which the operating
system is opting in.  If the BIOS or bootloader leaks bits here, this
is not desirable.  Consider a bootloader passing in %cr4.pae set to a
legacy paging kernel, for example -- it will not have any immediate
effect, but the kernel would crash when turning paging on.

A similar argument applies to %eflags, and since we have to look for
%eflags.id being settable we can use a sequence which clears %eflags
as a side effect.

Note that we already do this for x86-64.

Signed-off-by: H. Peter Anvin 
Link: 
http://lkml.kernel.org/r/1348529239-17943-1-git-send-email-...@linux.intel.com
---
 arch/x86/kernel/head_32.S |   31 ---
 1 files changed, 16 insertions(+), 15 deletions(-)

diff --git a/arch/x86/kernel/head_32.S b/arch/x86/kernel/head_32.S
index d42ab17..957a47a 100644
--- a/arch/x86/kernel/head_32.S
+++ b/arch/x86/kernel/head_32.S
@@ -287,27 +287,28 @@ ENTRY(startup_32_smp)
leal -__PAGE_OFFSET(%ecx),%esp
 
 default_entry:
-
 /*
  * New page tables may be in 4Mbyte page mode and may
  * be using the global pages. 
  *
  * NOTE! If we are on a 486 we may have no cr4 at all!
- * So we do not try to touch it unless we really have
- * some bits in it to set.  This won't work if the BSP
- * implements cr4 but this AP does not -- very unlikely
- * but be warned!  The same applies to the pse feature
- * if not equally supported. --macro
- *
- * NOTE! We have to correct for the fact that we're
- * not yet offset PAGE_OFFSET..
+ * Specifically, cr4 exists if and only if CPUID exists,
+ * which in turn exists if and only if EFLAGS.ID exists.
  */
-#define cr4_bits pa(mmu_cr4_features)
-   movl cr4_bits,%edx
-   andl %edx,%edx
-   jz 6f
-   movl %cr4,%eax  # Turn on paging options (PSE,PAE,..)
-   orl %edx,%eax
+   movl $X86_EFLAGS_ID,%ecx
+   pushl %ecx
+   popfl
+   pushfl
+   popl %eax
+   pushl $0
+   popfl
+   pushfl
+   popl %edx
+   xorl %edx,%eax
+   testl %ecx,%eax
+   jz 6f   # No ID flag = no CPUID = no CR4
+
+   movl pa(mmu_cr4_features),%eax
movl %eax,%cr4
 
testb $X86_CR4_PAE, %al # check if PAE is enabled
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/