aboutsummaryrefslogtreecommitdiff
path: root/sys/dev/nvme/nvme.c
diff options
context:
space:
mode:
authorWarner Losh <imp@FreeBSD.org>2019-07-18 21:58:51 +0000
committerWarner Losh <imp@FreeBSD.org>2019-07-18 21:58:51 +0000
commitc75bdc044d4dfc8d19954eac7e8a77fb256d58ba (patch)
treee04fc5c2c332acbcfbdaeec957198c9294c88b47 /sys/dev/nvme/nvme.c
parentf95dfdbe69ac186209f92609af95d2d99d3fa050 (diff)
downloadsrc-c75bdc044d4dfc8d19954eac7e8a77fb256d58ba.tar.gz
src-c75bdc044d4dfc8d19954eac7e8a77fb256d58ba.zip
Provide new tunable hw.nvme.verbose_cmd_dump
The nvme drive dumps only the most relevant details about a command when it fails. However, there are times this is not sufficient (such as debugging weird issues for a new drive with a vendor). Setting hw.nvme.verbose_cmd_dump=1 in loader.conf will enable more complete debugging information about each command that fails. Reviewed by: rpokala Sponsored by: Netflix Differential Version: https://reviews.freebsd.org/D20988
Notes
Notes: svn path=/head/; revision=350118
Diffstat (limited to 'sys/dev/nvme/nvme.c')
-rw-r--r--sys/dev/nvme/nvme.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/sys/dev/nvme/nvme.c b/sys/dev/nvme/nvme.c
index 84fe58a9f93e..449f2367c54f 100644
--- a/sys/dev/nvme/nvme.c
+++ b/sys/dev/nvme/nvme.c
@@ -54,6 +54,9 @@ struct nvme_consumer nvme_consumer[NVME_MAX_CONSUMERS];
uma_zone_t nvme_request_zone;
int32_t nvme_retry_count;
+int nvme_verbose_cmd_dump;
+
+TUNABLE_INT("hw.nvme.verbose_cmd_dump", &nvme_verbose_cmd_dump);
MALLOC_DEFINE(M_NVME, "nvme", "nvme(4) memory allocations");