HWSim.HomePage History

Hide minor edits - Show changes to markup - Cancel

Changed line 7 from:
  • Code of test application written with HWSim
to:
  • Code of test application written with HWSim
Changed line 7 from:
  • Code of test application written with HWSim
to:
  • Code of test application written with HWSim
January 25, 2015, at 12:43 AM by 65.183.45.146 -
Changed line 12 from:

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.

to:

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. Activities such as 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.

August 27, 2014, at 12:42 AM by 98.248.172.86 -
Changed line 10 from:

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.

to:

Nearly all open source 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 settings. 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.

August 27, 2014, at 12:41 AM by 98.248.172.86 -
Changed line 10 from:

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.

to:

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.

July 23, 2012, at 04:59 PM by 24.130.186.152 -
Changed lines 5-7 from:
to:
  • Project repo includes all sub-repositories, updated to correct versions to build the project
  • Code of HWSim language
  • Code of test application written with HWSim
July 19, 2012, at 04:52 PM by 24.130.186.152 -
Added line 2:
July 16, 2012, at 09:43 PM by 24.130.186.152 -
Changed line 9 from:

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.

to:

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.

July 16, 2012, at 09:38 PM by 24.130.186.152 -
Changed lines 1-2 from:

Welcome to VMS

to:

Welcome to HWSim

Deleted line 4:
July 16, 2012, at 09:38 PM by 24.130.186.152 -
Changed lines 1-7 from:
to:

Welcome to VMS

Introduction and Overview

July 16, 2012, at 09:35 PM by 24.130.186.152 -
Added lines 1-6:

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.

As a result, HWSim greatly speeds up the implementation of simulators for new architectures, by modularizing the implementation, allowing each behavior to be defined in isolation. It also eliminates the complications introduced by feedback paths in the architecture, and relieves the simulator implementor of concerns about the control flow and order of execution. All this, while simultaneously reducing time to wait for simulation results, by taking efficient advantage of parallel hardware.