From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: allow lightnvm to have visibility over AER events
Date: Fri, 13 Apr 2018 10:11:23 -0700 [thread overview]
Message-ID: <20180413171123.GA7732@infradead.org> (raw)
In-Reply-To: <1523619780-10882-2-git-send-email-javier@cnexlabs.com>
> enum {
> + /* valid bit mask */
> + NVM_LOGPAGE_STATE_MASK = 0x3,
> + NVM_LOGPAGE_SEVERITY_MASK = 0x5,
> +
> + /* scope */
> + NVM_LOGPAGE_SCOPE_SECTOR = 1,
> + NVM_LOGPAGE_SCOPE_CHUNK = 2,
> + NVM_LOGPAGE_SCOPE_LUN = 4,
> +
> + /* severity */
> + NVM_LOGPAGE_SEVERITY_LOW = 1,
> + NVM_LOGPAGE_SEVERITY_MID = 2,
> + NVM_LOGPAGE_SEVERITY_HIGH = 4,
> + NVM_LOGPAGE_SEVERITY_UNREC = 8,
> + NVM_LOGPAGE_SEVERITY_DEV = 16,
> +};
> +
> +struct nvm_log_page {
> + struct ppa_addr ppa;
> + u16 scope;
> + u8 severity;
> +};
> +
> +enum {
> /* Chunk states */
> NVM_CHK_ST_FREE = 1 << 0,
> NVM_CHK_ST_CLOSED = 1 << 1,
> diff --git a/include/linux/nvme.h b/include/linux/nvme.h
> index 4112e2bd747f..f85053601c5b 100644
> --- a/include/linux/nvme.h
> +++ b/include/linux/nvme.h
> @@ -440,6 +440,7 @@ enum {
> NVME_AER_VS = 7,
> NVME_AER_NOTICE_NS_CHANGED = 0x0002,
> NVME_AER_NOTICE_FW_ACT_STARTING = 0x0102,
> + NVME_AER_NOTICE_LNVM_CHUNK = 0xd00007,
> };
Non of these is in the NVMe spec or a ratified TP, so NAK.
next prev parent reply other threads:[~2018-04-13 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 11:42 [RFC PATCH] nvme: allow to handle AER events by kernel drivers Javier González
2018-04-13 11:43 ` [PATCH] nvme: allow lightnvm to have visibility over AER events Javier González
2018-04-13 15:27 ` Scott Bauer
2018-04-13 18:01 ` Javier Gonzalez
2018-04-13 16:58 ` Keith Busch
2018-04-13 17:55 ` Javier González
2018-04-16 9:16 ` Sagi Grimberg
2018-04-16 9:21 ` Javier González
2018-04-13 17:11 ` Christoph Hellwig [this message]
2018-04-13 17:20 ` Javier Gonzalez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180413171123.GA7732@infradead.org \
--to=hch@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.