aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorXunlei Pang <[email protected]>2017-07-12 14:33:17 -0700
committerLinus Torvalds <[email protected]>2017-07-12 16:25:59 -0700
commit5203f4995d9a87952a83c2ce7866adbbe8f97bb5 (patch)
tree6db0719c9edca7724eff0765f63ba184db535d8b /tools/perf/scripts/python/bin
parent203e9e41219b4e7357104e525e91ac609fba2c6c (diff)
powerpc/fadump: use the correct VMCOREINFO_NOTE_SIZE for phdr
vmcoreinfo_max_size stands for the vmcoreinfo_data, the correct one we should use is vmcoreinfo_note whose total size is VMCOREINFO_NOTE_SIZE. Like explained in commit 77019967f06b ("kdump: fix exported size of vmcoreinfo note"), it should not affect the actual function, but we better fix it, also this change should be safe and backward compatible. After this, we can get rid of variable vmcoreinfo_max_size, let's use the corresponding macros directly, fewer variables means more safety for vmcoreinfo operation. [[email protected]: fix build warning] Link: http://lkml.kernel.org/r/[email protected] Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Xunlei Pang <[email protected]> Reviewed-by: Mahesh Salgaonkar <[email protected]> Reviewed-by: Dave Young <[email protected]> Cc: Hari Bathini <[email protected]> Cc: Benjamin Herrenschmidt <[email protected]> Cc: Eric Biederman <[email protected]> Cc: Juergen Gross <[email protected]> Cc: Michael Holzheu <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions