Hey! Looks like whoever's e-mail account that was that was spewing error
messages to the list... stopped spewing errors.
BTW, is "En r�ponse �" a real language? Spanish? .fr = french?
Someone needs to organize CPU.CC's state. It's all messy. All the other
devices, like VGA.CC, PIC.CC, etc. store the state information in a "s"
structure. But not the CPU!
Here's an idea: make a CPU save_state and load_state. Then we can save
the entire plex86 state and restore it, like you can do in VMWare and
VirtualPC. Because all the devices and the RAM are easy to do... but for
the CPU I'd do this: call save_state which will fill in a "s" structure
that is to be created in the CPU class. That structure isn't "live", but
it can be "frozen" from all the structures in the CPU class. Thus it's
compact, fragmented, etc.; it'll have an EFLAGS field and so on.
load_state will load from the "s" structure to all the various CPU
structure elements.
Anyone else interested in this? It'd be cool.
christophe Bothamy wrote:
>
> En r�ponse � [EMAIL PROTECTED]:
>
> > Hi Kevin,
> >
> > I got ADSL access, ...
>
> Sh.t, i still have to learn the difference between "from" and "to".
> Sorry guys, this was meant to be a message for Kevin.
>
> Christophe.
