lkml.org 
[lkml]   [2005]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: 2.6.14: CR4 not needed to be inspected on the 486 anymore?
Date
From

On Mon, 7 Nov 2005, Zachary Amsden wrote:

> Maciej W. Rozycki wrote:
>
>> On Mon, 7 Nov 2005, Zachary Amsden wrote:
>>
>>
>>
>>> While this is at least no worse in the nested fault case than earlier
>>> kernels, I really wish I had one of those weird 486s so I could test the
>>> faulting mechanism. It seems the trap handling code has gotten quite
>>>
>>>
>>
>> What's so weird about 486s? Besides, for testing it doesn't have to be
>> one -- you will get away with a 386, too. I have neither anymore, but
>> there are people around still using them.
>>
>>
>
> Because I hold in my hand "i486 Microprocessor Programmer's Reference
> Manual, c 1990", and it has no mention whatsoever of CR4, and all
> documentation I had until Friday had either no mention of CR4, or
> something to the effect of "new on Pentium, the CR4 register ..." So
> I've had to re-adjust my definition of 486, which was weird.
>
> Zach
> -

Yes, and undocumented opcodes might not fault. They might do nothing
or something strange. It's not a good idea to use an undocumented
opcode in kernel space. The read-from-CR4 in kernel space, hoping
that an immoral-opcode trap will save you is not good practice.

You might reset the processor.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.13.4 on an i686 machine (5589.55 BogoMips).
Warning : 98.36% of all statistics are fiction.
.

****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-11-07 18:04    [W:0.072 / U:0.112 seconds]
©2003-2011 Jasper Spaans. Advertise on this site