Sounds good to me! Go for it!
On Thu, Aug 6, 2015 at 9:48 AM Andreas Sandberg <[email protected]> wrote: > Hi Everyone, > > I have recently been spending more time than I¹d like chasing a bugs > related to event autoserialization (Event::AutoSerialize). > > This is currently completely broken both for local events and global > events. I -- cough, cough -- may have been the one breaking local events, > but global events have been broken ever since they were introduced. > > I¹m leaning towards completely killing off the support for AutoSerialize. > AFAIK, the only place where this is used is the LinkDelay event, which > could quite easily be owned by the link and not the event queue. Doing > this would allow us to remove the fairly complicated dynamic object > creation code from the serialization framework and it would remove the > need to serialize event queues. A nice side effect is that it should make > it possible to load a checkpoint created with a multi-threaded > (multi-threaded checkpoints currently seem to be broken) gem5 into a > single-threaded gem5 since event queues wouldn¹t need to be serialized. > > Comments anyone? Steve? > > //Andreas > > > -- IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, > Registered in England & Wales, Company No: 2557590 > ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, > Registered in England & Wales, Company No: 2548782 > > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
