On 5/7/2019 10:58 AM, Akinobu Mita wrote:
This enables to capture snapshot of controller information via device coredump machanism.
s/machanism/mechanism/
The nvme device coredump creates the following coredump files. - regs: NVMe controller registers (00h to 4Fh) - sq<qid>: Submission queue - cq<qid>: Completion queue - telemetry-ctrl-log: Telemetry controller-initiated log (if available) - data: Empty The reason for an empty 'data' file is to provide a uniform way to notify the device coredump is no longer needed by writing the 'data' file. Since all existing drivers using the device coredump provide a 'data' file if the nvme device coredump doesn't provide it, the userspace programs need to know which driver provides what coredump file. Cc: Johannes Berg <[email protected]> Cc: Keith Busch <[email protected]> Cc: Jens Axboe <[email protected]> Cc: Christoph Hellwig <[email protected]> Cc: Sagi Grimberg <[email protected]> Cc: Minwoo Im <[email protected]> Signed-off-by: Akinobu Mita <[email protected]>
