summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/task-analyzer.py
diff options
context:
space:
mode:
authorJiaxun Yang <jiaxun.yang@flygoat.com>2023-02-21 16:16:58 +0300
committerThomas Bogendoerfer <tsbogend@alpha.franken.de>2023-03-14 19:06:16 +0300
commit7b76ab837522fd6aa72b25d1c5460995095fedc0 (patch)
treed1768e1ee3e73429e6b2e9b99076588aa6efb1b8 /tools/perf/scripts/python/task-analyzer.py
parent162e134aedcacc9ab9d5648349ceb5409f9ec880 (diff)
downloadlinux-7b76ab837522fd6aa72b25d1c5460995095fedc0.tar.xz
MIPS: Loongson64: Opt-out war_io_reorder_wmb
It is clearly stated on "Loongson 3A3000/3B3000 processor user manual vol 2" that "All access requests using a non-cached algorithm are executed in a blocking order. That is, before the current read request data is returned to the processor, all subsequent requests are blocked and issued; All subsequent requests are blocked until the write request data has been sent or the issued write request has not received a write reply from the final receiver." Which means uncached read/write is strongly ordered. So we won't need this workaround. This option was introduced when we add initial support for GS464E, it looks like a misinterpretation of another section in the manual saying we need barriers to ensure MMIO order against DMA requests. Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions