gem5 retire and store completion stages about konata HOT 5 OPEN

Hello,

Regarding "retire", I remember that I implemented it so that the entire pipeline ends there, for ease of implementation. This is because it is a bit difficult in Konata to record events (stages) where there is no command to trigger the end of the stage, such as retire ("retire" is the last command of each instruction).

"retire" exists next to the end of "complete" stages, do you think this should be shown? If there is any advantage to explicitly displaying it, I would consider modifying it.

Regarding "mem_complete", I was not aware of "--store_completions", so I don't think it is implemented. I would like to modify Konata to support this.

from konata.

I found and remembered an implementation of "mem_complete" in the parser, but it does not support logs output by O3PipeView with "--store_completions". This part is related to a feature for parsing miscellaneous logs output by O3CPUAll and showing additional information.

from konata.

@shioyadan - actual execution of store operation happens after signal from "retire" stage, so "--store_completions" helps to see store latency which may be useful for example for cache write policy analysis.

In gem5 viewer "retire" stage is displayed for each instruction and store marker is additionally displayed for store instructions. I think for Konata it makes sense to use similar approach to keep stages scheme aligned with gem5 viewer.

from konata.

Agree with mshiryaev,

without processing with "retire", all the commit stage will be at least 2 cycles, and even those been flushed will have 1 cycle "commit", which is a bit confusing :)

from konata.

@mshiryaev @shuheque
Thank you for your explanation.
I understand that it is better to show retirement/store stages.
I will modify the parser to add the feature. Please wait a while.

from konata.