diff options
| author | Zachary Amsden <zach@vmware.com> | 2006-01-06 00:11:50 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-01-06 08:33:34 -0800 |
| commit | ff6e8c0d5e47f0ceeebde86ec2f5919dbd5beb67 (patch) | |
| tree | f7e50b5962b7b38ca025c0bf9ee48b618424cc6b /arch | |
| parent | eb05c3249a8e8a675e79d221f4a0874dc10ec903 (diff) | |
| download | op-kernel-dev-ff6e8c0d5e47f0ceeebde86ec2f5919dbd5beb67.zip op-kernel-dev-ff6e8c0d5e47f0ceeebde86ec2f5919dbd5beb67.tar.gz | |
[PATCH] x86: Cr4 is valid on some 486s
So some 486 processors do have CR4 register. Allow them to present it in
register dumps by using the old fault technique rather than testing processor
family.
Thanks to Maciej for noticing this.
Signed-off-by: Zachary Amsden <zach@vmware.com>
Cc: "Seth, Rohit" <rohit.seth@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch')
| -rw-r--r-- | arch/i386/kernel/process.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/arch/i386/kernel/process.c b/arch/i386/kernel/process.c index 2333aea..6081a10 100644 --- a/arch/i386/kernel/process.c +++ b/arch/i386/kernel/process.c @@ -308,9 +308,7 @@ void show_regs(struct pt_regs * regs) cr0 = read_cr0(); cr2 = read_cr2(); cr3 = read_cr3(); - if (current_cpu_data.x86 > 4) { - cr4 = read_cr4(); - } + cr4 = read_cr4_safe(); printk("CR0: %08lx CR2: %08lx CR3: %08lx CR4: %08lx\n", cr0, cr2, cr3, cr4); show_trace(NULL, ®s->esp); } |
