Messages in this thread | | | Date | Wed, 26 Jul 2000 16:06:45 +0100 (BST) | From | James Sutherland <> | Subject | Re: Direct access to hardware |
| |
On Wed, 26 Jul 2000, Stephen Frost wrote:
> On Wed, 26 Jul 2000, James Sutherland wrote: > > > 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. > > Erm, the OS basically tells the CPU to handle it, so the OS doesn't > have to worry about it. The OS certainly doesn't sit and check every > instruction being sent to the CPU is valid. The parallel to IDE would be > sending an initial command to the drive saying "Don't let me touch your > firmware" on boot and then never having to think about it again. This > would be a relatively small patch (if it was supported by the drive) I > suspect and probably would go in with no problem.
That's Andre's current plan, so what's the problem?
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/
| |