Hey Kevin,
Do you think that maybe looking into somehow optimising the resultant
assembler code from the plex86 codebase would help speed up the final
virtualization code?  I know that you make your actual assembly work as fast
as possible, but could we get any observable gains from optimising the C/C++
portions of this project in a more "hands-on" way?

Drew Northup, N1XIM


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Kevin Lawton
> Sent: Wednesday, November 01, 2000 1:14 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [plex86] CVS updates
>
>
> "Kenneth C. Arnold" wrote:
> >
> > On Tue, Oct 31, 2000 at 05:51:28PM -0500, Kevin Lawton wrote:
> > > Just minor additions.  Beginning the task of filling out some more
> > > protected mode emulation; code transitions, task switches, etc.
> > > Need some more of this before trying to run Windows.
> >
> > ... and VGA, considering that Windows is pretty heavily graphics-bound.
>
> That shouldn't be a problem.  VGA emulation is already in plex86.
> Graphics modes too.  Just need to write protect the physical memory
> range designated for video, and redirect 'uncacheable' memory
> accesses to the existing video emulation.  This won't
> be fast, but it will let us get started.
>
> I'm going to do that soon.  But first, the emulation code...
>
>
>
> -Kevin
>
>


Reply via email to