[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1515592429-17420-1-git-send-email-aspriel@gmail.com>
Date: Wed, 10 Jan 2018 14:53:46 +0100
From: Arend van Spriel <aspriel@...il.com>
To: Greg Koah Hartmann <gregkh@...uxfoundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Arend van Spriel <aspriel@...il.com>
Subject: [PATCH V2 0/3] sysfs: allow user-space request for devcoredump
Since commit 833c95456a70 ("device coredump: add new device coredump class")
device drivers have a unified way to provide binary data obtained from a
failing_device to user-space. However, there may be use-cases in which the
driver has no reason to obtain the data, but user-space wants to initiate
it. This adds a coredump device attribute in sysfs when the driver bound to
the device supports the newly added coredump driver callback. As the
devcoredump API offers more than one option, eg. single buffer vs. scatter
list, it is left up to the driver how to invoke the devcoredump API. As an
example this series includes a driver implementation as RFC. There are other
drivers having some form of device firmware coredump that could benefit
from this, but decided to tackle that in another cycle.
These patches apply to the driver-core-next branch of the driver-core
repository.
Arend van Spriel (3):
sysfs: add attribute specification for /sysfs/devices/.../coredump
drivers: base: add coredump driver ops
brcmfmac: pcie: implement .coredump() driver callback
Documentation/ABI/testing/sysfs-devices-coredump | 10 ++++++
drivers/base/dd.c | 40 ++++++++++++++++++----
.../wireless/broadcom/brcm80211/brcmfmac/pcie.c | 22 ++++++++++++
include/linux/device.h | 2 +-
4 files changed, 66 insertions(+), 8 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-devices-coredump
--
1.9.1
Powered by blists - more mailing lists