summaryrefslogtreecommitdiffstats
path: root/init
diff options
context:
space:
mode:
authorRahul Lakkireddy <rahul.lakkireddy@chelsio.com>2018-05-02 15:17:17 +0530
committerDavid S. Miller <davem@davemloft.net>2018-05-14 13:46:04 -0400
commit2724273e8fd00b512596a77ee063f49b25f36507 (patch)
treed814285445675db025d5b4f3cf9eaf088466eefd /init
parent289e1f4e9e4a09c73a1c0152bb93855ea351ccda (diff)
downloadlinux-2724273e8fd00b512596a77ee063f49b25f36507.tar.bz2
vmcore: add API to collect hardware dump in second kernel
The sequence of actions done by device drivers to append their device specific hardware/firmware logs to /proc/vmcore are as follows: 1. During probe (before hardware is initialized), device drivers register to the vmcore module (via vmcore_add_device_dump()), with callback function, along with buffer size and log name needed for firmware/hardware log collection. 2. vmcore module allocates the buffer with requested size. It adds an Elf note and invokes the device driver's registered callback function. 3. Device driver collects all hardware/firmware logs into the buffer and returns control back to vmcore module. Ensure that the device dump buffer size is always aligned to page size so that it can be mmaped. Also, rename alloc_elfnotes_buf() to vmcore_alloc_buf() to make it more generic and reserve NT_VMCOREDD note type to indicate vmcore device dump. Suggested-by: Eric Biederman <ebiederm@xmission.com>. Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com> Signed-off-by: Ganesh Goudar <ganeshgr@chelsio.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions