From: hch@lst.de (Christoph Hellwig)
Subject: [PATCHv3 5/5] nvme: Send uevent for some asynchronous events
Date: Thu, 9 Nov 2017 10:27:03 +0100 [thread overview]
Message-ID: <20171109092702.GE17120@lst.de> (raw)
In-Reply-To: <20171107221314.27822-6-keith.busch@intel.com>
On Tue, Nov 07, 2017@03:13:14PM -0700, Keith Busch wrote:
> This will give udev a chance to observe and handle asynchronous event
> notifications and clear the log to unmask future events of the same type.
> The driver will create a change uevent of the asyncronuos event result
> before submitting the next AEN request to the device if a completed AEN
> event is of type error, smart, command set or vendor specific,
>
> Signed-off-by: Keith Busch <keith.busch at intel.com>
> ---
> drivers/nvme/host/core.c | 28 ++++++++++++++++++++++++++++
> drivers/nvme/host/nvme.h | 1 +
> include/linux/nvme.h | 4 ++++
> 3 files changed, 33 insertions(+)
>
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index f5e059af65cc..486d02204c5d 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -2678,11 +2678,28 @@ void nvme_remove_namespaces(struct nvme_ctrl *ctrl)
> }
> EXPORT_SYMBOL_GPL(nvme_remove_namespaces);
>
> +static void nvme_aen_uevent(struct nvme_ctrl *ctrl)
> +{
> + char *envp[2] = {NULL, NULL};
> + u32 aen = ctrl->aen;
> +
> + ctrl->aen = 0;
Seems like we should use cmpxchg on aen.
> + if (!aen)
> + return;
> +
> + envp[0] = kasprintf(GFP_KERNEL, "NVME_AEN=%#08x", aen);
> + if (!envp[0])
> + return;
> + kobject_uevent_env(&ctrl->device->kobj, KOBJ_CHANGE, envp);
> + kfree(envp[0]);
> +}
> +
> static void nvme_async_event_work(struct work_struct *work)
> {
> struct nvme_ctrl *ctrl =
> container_of(work, struct nvme_ctrl, async_event_work);
>
> + nvme_aen_uevent(ctrl);
> ctrl->ops->submit_async_event(ctrl);
> }
>
> @@ -2754,6 +2771,17 @@ void nvme_complete_async_event(struct nvme_ctrl *ctrl, __le16 status,
> if (le16_to_cpu(status) >> 1 != NVME_SC_SUCCESS)
> return;
>
> + switch (result & 0x7) {
> + case NVME_AER_ERROR:
> + case NVME_AER_SMART:
> + case NVME_AER_CSS:
> + case NVME_AER_VS:
> + ctrl->aen = result;
Can we call the field aen_result?
Given that the rest of the series looks good I'd be tempted to just
fix that up and apply it. Are you ok with that?
next prev parent reply other threads:[~2017-11-09 9:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 22:13 [PATCHv3 0/5] Asynchronous events for udev Keith Busch
2017-11-07 22:13 ` [PATCHv3 1/5] nvme: Centralize AEN defines Keith Busch
2017-11-08 1:37 ` Guan Junxiong
2017-11-09 9:23 ` Christoph Hellwig
2017-11-07 22:13 ` [PATCHv3 2/5] nvme/fc: remove unused "queue_size" field Keith Busch
[not found] ` <45c5bfad-4854-2e01-905e-bcd8cbf42314@broadcom.com>
2017-11-08 0:04 ` Keith Busch
2017-11-08 1:38 ` Guan Junxiong
2017-11-09 9:23 ` Christoph Hellwig
2017-11-07 22:13 ` [PATCHv3 3/5] nvme: Single AEN request Keith Busch
2017-11-08 1:35 ` Guan Junxiong
2017-11-09 9:24 ` Christoph Hellwig
2017-11-09 16:04 ` Keith Busch
2017-11-09 9:25 ` Christoph Hellwig
2017-11-07 22:13 ` [PATCHv3 4/5] nvme: Unexport starting async event work Keith Busch
2017-11-08 1:39 ` Guan Junxiong
2017-11-07 22:13 ` [PATCHv3 5/5] nvme: Send uevent for some asynchronous events Keith Busch
2017-11-08 1:40 ` Guan Junxiong
2017-11-09 9:27 ` Christoph Hellwig [this message]
2017-11-09 16:18 ` Keith Busch
2017-11-09 16:23 ` Christoph Hellwig
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=20171109092702.GE17120@lst.de \
--to=hch@lst.de \
/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.