Re: Direct access to hardware

From: James Sutherland (jas88@cam.ac.uk)
Date: Wed Jul 26 2000 - 05:56:55 EST


On 25 Jul 2000, Krzysztof Halasa wrote:

> James Sutherland <jas88@cam.ac.uk> writes:
>
> > On Tue, 25 Jul 2000, Stuart MacDonald wrote:
> >
> > > Which is exactly the point. The hard drives should be checking for
> > > invalid ATA commands in hardware, right in the drive, preventing
> > > damage from bad commands. Putting a filter into the kernel is not
> > > the right fix.
> >
> > As with some of the Intel CPU bugs, the problem is NOT "invalid ATA
> > commands" - it's a matter of VALID commands which are dangerous. FDIV on
> > early Pentiums isn't an invalid instruction - it just produces the wrong
> > results at times. So the SOFTWARE must do something to avoid this - either
> > that, or you need to replace the hardware, which isn't desirable. You do
> > something in the OS to prevent these problem commands being used.
>
> So what does the kernel (can) do to prevent this problem on defective
> pentiums?

Trap the defective instructions, and implement a replacement instruction
in software. On later Intel CPUs, you can sometimes use a microcode update
to fix it - this also requires OS intervention.

Either way, essentially you tell the OS to block the duff instructions,
and it does so.

James.

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



This archive was generated by hypermail 2b29 : Mon Jul 31 2000 - 21:00:21 EST