Re: [Gems-users] LogTM bug: no reset on overflow bit!

[郭锐 <timmyguo@xxxxxxxxxxxxxxxx>]

An extra note. There have already been 'Overflow' functions in the
TransactionManger. But it's never called at all. Maybe forgotten by the
authors?
> -----Original Message-----
> From: gems-users-bounces@xxxxxxxxxxx
[mailto:gems-users-bounces@xxxxxxxxxxx]
> On Behalf Of 郭锐
> Sent: Thursday, August 09, 2007 11:27 AM
> To: gems-users@xxxxxxxxxxx
> Subject: [Gems-users] LogTM bug: no reset on overflow bit!
> 
> I ran into a protocol problem recently, and find that the overflow bit
> doesn't get cleared properly at transaction commit. This bug exists in
both
> of the MOESI and the MESI version of the LogTM protocol. The GEMS version
I
> use is v1.4.
> 
> A possible fix to this bug is just move the overflow bit from the cache
> controller to the TransactionManager. Because there is no special cache
> request to cache controller whenever a transaction is to be committed.
> 
> G.R.
> 
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> Use Google to search the GEMS Users mailing list by adding
> "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.