[A83] Re: microcode

To: assembly-83@lists.ticalc.org
Subject: [A83] Re: microcode
From: Gavin Olson <gtolson@snet.net>
Date: Tue, 18 Sep 2001 21:45:16 -0400
In-Reply-To: <5.1.0.14.0.20010918204732.04201008@pop.home.se>
References: <5.1.0.14.0.20010918144239.00a29810@pop.snet.net> <F263HArFQmHjAv5bJVx0001661a@hotmail.com>
Reply-To: assembly-83@lists.ticalc.org


At 08:51 PM 9/18/2001 +0200, you wrote:

>At 20:44 2001-09-18, you wrote:
> >Updating microcode is probably a complex process, that cannot be easily
> >done by software running on said processor.  The worst I've heard of is one
> >that flashes your BIOS with garbage, then reboots.  The only way I can
> >think of that a processor could contro lthe operation to recode itself
> >wouldbe if there were two processors, and most people aren't that rich . . .
>
>It could also have a small and simple "bootstrap" that loads itself with
>new microcode.
>It would be very possible construct it to put a memory adress in a register
>and call a certain instruction or something.
>Doesn't feel likly it is done like that though, to much safety problems :)
>I didn't know about this new capability of new Intel processors. Sounds
>very interesting.
>Will see if I can find some more info on it.
>
>///Olle


Such a virus would also be expensive to test, with a minimum being the cost 
of a brand new PIII or P4.

References:

[A83] Re: microcode

From: Gavin Olson <gtolson@snet.net>

[A83] Re: microcode

From: "Jimmy Pardey" <j_pardey@hotmail.com>

[A83] Re: microcode

From: Olle Hedman <alh@home.se>