Some instructions (zerroall, zeroupper, etc.) don't have any modeled throughput values. The patch suggests usage of latency as throughput values in such cases.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
I'm not sure we need rebase this patch because 2 pre-patches do almost everything I'd like to see here. There is only one last thing: a possibilty to return latency as value of throughput if we don't have any sched model or don't have ResourceCycles in the existing model. But now I think that programmer can do this functionality by himself (if s/he needs it). Am I right? I'm going to abandon this review. OK?
Aren't this change (and its equivalent in the next function) separate patches that need to go in first?