[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180424.155452.825338057383489874.davem@davemloft.net>
Date: Tue, 24 Apr 2018 15:54:52 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: rahul.lakkireddy@...lsio.com
Cc: netdev@...r.kernel.org, kexec@...ts.infradead.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
viro@...iv.linux.org.uk, ebiederm@...ssion.com,
stephen@...workplumber.org, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org, ganeshgr@...lsio.com,
nirranjan@...lsio.com, indranil@...lsio.com
Subject: Re: [PATCH net-next v5 0/3] kernel: add support to collect
hardware logs in crash recovery kernel
From: Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>
Date: Sat, 21 Apr 2018 22:35:52 +0530
> Patch 1 adds API to vmcore module to allow drivers to register callback
> to collect the device specific hardware/firmware logs. The logs will
> be added to /proc/vmcore as elf notes.
>
> Patch 2 updates read and mmap logic to append device specific hardware/
> firmware logs as elf notes.
>
> Patch 3 shows a cxgb4 driver example using the API to collect
> hardware/firmware logs in crash recovery kernel, before hardware is
> initialized.
Are there any serious remaining objections to this series? I'm going to
integrate this into net-next soon if not.
Thank you.
Powered by blists - more mailing lists