summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorNam Cao <namcao@linutronix.de>2024-06-07 23:22:06 +0300
committerPalmer Dabbelt <palmer@rivosinc.com>2024-09-12 17:22:55 +0300
commitaa3457f22f00b9c9039672b1ff942fd72a5330d8 (patch)
treef7abc73171cecb360d271de2d856a96405748258 /tools/perf/scripts/python/exported-sql-viewer.py
parent57d76bc51fd80824bcc0c84a5b5ec944f1b51edd (diff)
downloadlinux-aa3457f22f00b9c9039672b1ff942fd72a5330d8.tar.xz
riscv: cleanup XIP_FIXUP macro
The XIP_FIXUP macro is used to fix addresses early during boot before MMU: generated code "thinks" the data section is in ROM while it is actually in RAM. So this macro corrects the addresses in the data section. This macro determines if the address needs to be fixed by checking if it is within the range starting from ROM address up to the size of (2 * XIP_OFFSET). This means if the kernel size is bigger than (2 * XIP_OFFSET), some addresses would not be fixed up. XIP kernel can still work if the above scenario does not happen. But this macro is obviously incorrect. Rewrite this macro to only fix up addresses within the data section. Signed-off-by: Nam Cao <namcao@linutronix.de> Reviewed-by: Alexandre Ghiti <alexghiti@rivosinc.com> Link: https://lore.kernel.org/r/95f50a4ec8204ec4fcbf2a80c9addea0e0609e3b.1717789719.git.namcao@linutronix.de Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions