Yes if you are looking at master branch. - Avadh
On Thu, Jun 30, 2011 at 12:47 PM, Ching-Tsun Chou <[email protected]>wrote: > I dug around a bit and found that QEMU > commit 6173d56bdcb53389c54e803873e6bf8f87836a4f (tag v0.12.3) is still the > one closest to the qemu subdirectory in Marss. > > - Ching Tsun > > On Thu, Jun 30, 2011 at 7:43 AM, avadh patel <[email protected]> wrote: > >> >> On Wed, Jun 29, 2011 at 9:15 PM, Ching-Tsun Chou < >> [email protected]> wrote: >> >>> What are the Git SHA-1 ids of the QEMU and PTLsim commits that MARSS >>> uses? For example, the QEMU commit that MARSS uses seems to be almost the >>> one with the tag "v0.12.3", but not exactly. Which QEMU commit is the last >>> one merged into MARSS? Similar question for PTLsim. >>> >>> On the master branch you'll not see any SHA1/Commit Messages from either >> QEMU or PTLsim. Its because we started with our internal highly modified >> PTLsim version so it was never linked to PTLsim's git repo. About QEMU, we >> started with its released version 0.10 and then upgraded it to 0.12.3 but >> all from their released archive. >> >> If you take a look at 'qemu-0.14' branch or 'core-models' branch then >> you'll see that we merged 0.14.1 release. Qemu's git tree is too large and >> merging its history with Marss will make things a lot confusing at this >> point. In 'qemu-0.14' branch last SHA1 from Qemu's tree is: >> >> 56a60dd6d619877e9957ba06b92d2f276e3c229d >> >> Hope this helps in solving your issue. >> >> - Avadh >> >> >> I'd like to learn what changes MARSS needs to make in QEMU and PTLsim. >>> >>> Thanks! >>> - Ching Tsun >>> >>> _______________________________________________ >>> http://www.marss86.org >>> Marss86-Devel mailing list >>> [email protected] >>> https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel >>> >>> >> >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
