If you're looking for "bad" patterns like linked-list or tree traversal, you'd be looking for loads whose address depends on another recent load (not including loads from locals on the stack, like [rsp+const] addressing modes, unless store/reload is part of a chain). IDK if PIN can help detect such patterns.

如果您正在寻找像链表或树遍历这样的“坏”模式，那么您将寻找其地址依赖于另一个最近加载的加载(不包括来自堆栈上的本地加载的加载，如[RSP+Const]寻址模式，除非存储/重新加载是链的一部分)。如果PIN可以帮助检测此类模式，请确认。

Other than that, the main things I'd look for would be loads that tend to miss in cache, especially ones that end up stalling execution. e.g. on Intel (such as Skylake), there's an event cycle_activity.stalls_l3_miss which might be one to look for: Execution stalls while L3 cache miss demand load is outstanding. An "execution stall" is when no uops are dispatched from the scheduler to an execution unit that cycle. There are lots of other events for cache misses in various levels, and lines in/out.

除此之外，我要寻找的主要内容是缓存中往往未命中的加载，特别是那些最终导致执行停滞的加载。例如，在英特尔(如Skylake)上，有一个事件Cycle_Activity.stalls_L3_Misse可能是要查找的：当L3缓存未命中请求加载未完成时，执行暂停。“执行停顿”是指没有微指令从调度器调度到该周期的执行单元。对于不同级别的高速缓存未命中以及行输入/输出，还有许多其他事件。