* [[http://hg.opensourceresearchinstitute.org/cgi-bin/hgwebdir.cgi/PR/Applications/HWSim/HWSim__PingPong__HWDef/file/b1c9d67643f2|Code of test application written with HWSim]]

* [[http://hg.opensourceresearchinstitute.org/cgi-bin/hgwebdir.cgi/VMS/Applications/HWSim/HWSim__PingPong__HWDef/file/b1c9d67643f2|Code of test application written with HWSim]]

We present a domain-specific parallel language that handles the parallel aspects, so that writing a new simulator reduces to just defining the behavior of architectural elements, using sequential reasoning. The language, called HWSim, provides constructs for defining elements and attaching to them functions that represent their behavior. The advancement of time and control over the order of physically executing the behaviors takes place inside HWSim, which ensures that the Host memory state is always consistent with what the Guest memory state would be at the point that behavior for a given point in simulated time is physically executed.

Nearly all open source architectural simulators available are written as sequential code, and converting them to use multiple cores during simulation has proven daunting for it to be undertaken within Open Source simulators. The advantage of a parallel simulator implementation would be shorter time until an answer is available, which speeds up the design cycle for hardware, which is especially important during the early exploratory phase of new architecture designs.

Nearly all architectural simulators available are written as sequential code, and converting them to use multiple cores during simulation has proven too daunting for it to be undertaken within Open Source simulators. The advantage of a parallel simulator implementation would be shorter time until an answer is available, which speeds up the design cycle for hardware, which is especially important during the early exploratory phase of new architecture designs.

We present a domain-specific parallel language that handles the parallel aspects, so that writing a new simulator reduces to just defining the behavior of architectural elements, using sequential reasoning. The language, called HWSim, provides constructs for defining elements and attaching functions that represent their behavior. The advancement of time and control over the order of physically executing the behaviors takes place inside HWSim, which ensures that the Host memory state is always consistent with what the Guest memory state would be at the point that behavior for a given point in simulated time is physically executed.

!Welcome to VMS