summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorAshish Kalra <ashish.kalra@amd.com>2025-05-06 18:35:29 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-05-22 14:31:52 +0200
commit3822556c977b779e4f109ed9f412dd095e1f46a8 (patch)
treed38ffc168c47c71578eb9e328e0d963d6a35840b /tools/perf/scripts/python/stackcollapse.py
parent26468ea864fecf496654459e52a6b7a7230bcb6d (diff)
downloadkernel-3822556c977b779e4f109ed9f412dd095e1f46a8.tar.gz
x86/sev: Make sure pages are not skipped during kdump
commit 82b7f88f2316c5442708daeb0b5ec5aa54c8ff7f upstream. When shared pages are being converted to private during kdump, additional checks are performed. They include handling the case of a GHCB page being contained within a huge page. Currently, this check incorrectly skips a page just below the GHCB page from being transitioned back to private during kdump preparation. This skipped page causes a 0x404 #VC exception when it is accessed later while dumping guest memory for vmcore generation. Correct the range to be checked for GHCB contained in a huge page. Also, ensure that the skipped huge page containing the GHCB page is transitioned back to private by applying the correct address mask later when changing GHCBs to private at end of kdump preparation. [ bp: Massage commit message. ] Fixes: 3074152e56c9 ("x86/sev: Convert shared memory back to private on kexec") Signed-off-by: Ashish Kalra <ashish.kalra@amd.com> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com> Tested-by: Srikanth Aithal <sraithal@amd.com> Cc: stable@vger.kernel.org Link: https://lore.kernel.org/20250506183529.289549-1-Ashish.Kalra@amd.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions