aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c
diff options
context:
space:
mode:
authorIlya Leoshkevich <[email protected]>2025-05-15 15:52:11 +0000
committerAndrew Morton <[email protected]>2025-05-21 17:48:24 +0000
commit3545414f2590177a76f86c985130dc4824d3adc9 (patch)
treedd3642ee221b1ae4771d844bd136a912ba5ba9c9 /drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c
parentkernel/panic.c: format kernel-doc comments (diff)
downloadkernel-3545414f2590177a76f86c985130dc4824d3adc9.tar.gz
kernel-3545414f2590177a76f86c985130dc4824d3adc9.zip
scripts/gdb/symbols: factor out get_vmlinux()
Patch series "scripts/gdb/symbols: determine KASLR offset on s390 during early boot". I noticed that debugging s390 early boot using the support I introduced in commit 28939c3e9925 ("scripts/gdb/symbols: determine KASLR offset on s390") does not work. The reason is that decompressor does not provide the vmcoreinfo note, so KASLR offset needs to be extracted in a different way, which this series implements. Patches 1-2 are trivial refactorings, and patch 3 is the implementation. This patch (of 3): Move the code that determines the current vmlinux file into a separate function. It will be useful later in order to analyze the kernel image in physical memory during s390 early boot. Link: https://lkml.kernel.org/r/[email protected] Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Ilya Leoshkevich <[email protected]> Cc: Alexander Gordeev <[email protected]> Cc: Heiko Carstens <[email protected]> Cc: Jan Kiszka <[email protected]> Cc: Kieran Bingham <[email protected]> Cc: Vasily Gorbik <[email protected]> Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c')
0 files changed, 0 insertions, 0 deletions