[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eb4f578c-2126-c4e8-97a9-2f65e4784359@intel.com>
Date: Tue, 7 May 2019 11:44:58 -0600
From: "Heitke, Kenneth" <kenneth.heitke@...el.com>
To: Akinobu Mita <akinobu.mita@...il.com>,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: Jens Axboe <axboe@...com>, Sagi Grimberg <sagi@...mberg.me>,
Keith Busch <keith.busch@...el.com>,
Minwoo Im <minwoo.im.dev@...il.com>,
Johannes Berg <johannes@...solutions.net>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v2 6/7] nvme-pci: add device coredump support
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 <johannes@...solutions.net>
> Cc: Keith Busch <keith.busch@...el.com>
> Cc: Jens Axboe <axboe@...com>
> Cc: Christoph Hellwig <hch@....de>
> Cc: Sagi Grimberg <sagi@...mberg.me>
> Cc: Minwoo Im <minwoo.im.dev@...il.com>
> Signed-off-by: Akinobu Mita <akinobu.mita@...il.com>
Powered by blists - more mailing lists