Re: VGA emulation in BOCHS

i am experimenting with parallelizing BOCHS. there are a few things i
have done to bring paraBOCHS to the current state.

1. put cpu in separate threads.
2. make the code cache thread safety
3. exclusively locked the page when atomic instructions are emulated.
4. i am currently solving the x window problem.

right now only the thread that is running BX_CPU(0) is calling the
currCountDown, but i still get assertion from the libX library. could
any other CPU thread be calling functions in libX at the same time if
they run truly in parallel ?

Xin

On Fri, Oct 19, 2012 at 8:14 AM, Volker Ruppert
<[email protected]> wrote:
> Hi!
>
>
>> I am now running BOCHS emulated CPUs in parallel ( i.e. on separate
>> host os threads). only the  BX_CPU(0) is decrementing the
>> countDownEvent. However, i get an assertion in libx11.so shared
>> library when i run many CPUs ( i.e. 8 CPUs). i suspect it is due to
>> the fact that the libx11 is not thread safe and more than 1 CPUs are
>> working in the x.cc code.   If only BX_CPU(0)  is decrementing the
>> countDownEvent. can other thread also have access to anything in the
>> GUI ?
>
>
> What do you mean with "running CPUs in separate threads" ?
> With the official Bochs SVN code you can only do this:
>
> 1. one Bochs instance with all CPUs running in the same thread
> 2. multiple Bochs instances (works with X11)
>
> Yes, the Xlib is not thread safe and our code in x.cc has not yet been
> tested with the display update called from another thread. The SDL,
> wxWidgets and win32 gui implementations should already be able to work in
> this case.
>
> --
> Thanks
>
> Volker
>

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct