Hi Everyone, For many of my experiments, I need to forward begin/end work item notifications to my simulation scripts. We currently have support for workBegin / workEnd m5op annotations that take a work item id as a parameter. These instructions do exactly what I need from the guest¹s point of view. However, the current implementation is both inflexible (all logic is in C++ and the maximum number of work items need to be known a priori) and hard to understand (it relies on 8(!) parameters in System).
I have on multiple occasions in the past found the need to make callbacks to my simulation scripts. So far, I have mainly relied on hacks, but I¹d like to fix this once and for all. I currently have a patch that rips out all the C++ work item logic and replaces it with simulator exits that include the work ID. Is this something that¹d be useful to others? Is anyone using the current work annotation support? Also, do we need a more general simulation script callback/annotation mechanism? I have in the past used m5exits to tell my simulation script what the guest is doing (e.g., boot done, starting benchmark, benchmark done, verifying output, Š) and just resumed simulation if the exit code was in a non-fatal range. Regards, 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. _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
