Re: [Gems-users] addLogEntry and addMagicEntry

[Jayaram Bobba <bobba@xxxxxxxxxxx>]

Yet to be released.

Jayaram

James Wang wrote:
> Hi Jayaram:
> 	By current code, do you mean GEMS 1.2 or something that is yet to be
> released?
> Regards
> James
>
> -----Original Message-----
> From: gems-users-bounces@xxxxxxxxxxx [mailto:gems-users-bounces@xxxxxxxxxxx]
> On Behalf Of Jayaram Bobba
> Sent: Sunday, May 21, 2006 4:46 PM
> To: Gems Users
> Subject: Re: [Gems-users] addLogEntry and addMagicEntry
>
> Hi James
>
> addLogEntry creates the undo log entry when a transactional store is 
> completed.
> addMagicEntry is a simulation artifact. When a transactional store needs 
> to be
> 'aborted', we unstall simics and allow it to complete the store. 
> However, we make
> note of it in a 'Magic' entry and then unroll the store two cycles 
> later. It is an ugly
> hack. In our current code, we have worked around it by raising an exception
> instead, on the aborted store. You can use the 'exception' field in 
> generic_transaction_t
> to do this.
>
> regards
> Jayaram
>
> James Wang wrote:
>   
> > Hi All:
> >     I am reading the LogTM source code, and in the
> > TransactionLog class, there are two methods:
> > addLogEntry and addMagicEntry. How do these two
> > methods differ? What is a magic entry?
> >     Thanks in advance.
> >
> >
> > Regards
> > James
> > _______________________________________________
> > Gems-users mailing list
> > Gems-users@xxxxxxxxxxx
> > https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> >   
> >     
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>