From: Toomas Soome <tsoome@me.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1747393] Re: nvme is missing support for NVME_ADM_CMD_ASYNC_EV_REQ
Date: Thu, 08 Feb 2018 17:32:07 -0000 [thread overview]
Message-ID: <151811112806.27805.4234071796130648960.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 151782642980.10198.17726074601611845094.malonedeb@wampee.canonical.com
** Description changed:
NVME_ADM_CMD_ASYNC_EV_REQ is required by specification but apparently we
will be responded by error when this command is used.
+
+ The Asynchronous Event Request is a mandatory opcode required by
+ specification (Figure 40, Section 5 in NVMe 1.2; Figure 41, Section 5 in
+ NVMe 1.3). A simple way to deal with this in an emulator that doesn't
+ really want to use async events is to queue up the requests and not do
+ anything with them, and only complete them when the driver aborts the
+ command.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1747393
Title:
nvme is missing support for NVME_ADM_CMD_ASYNC_EV_REQ
Status in QEMU:
New
Bug description:
NVME_ADM_CMD_ASYNC_EV_REQ is required by specification but apparently
we will be responded by error when this command is used.
The Asynchronous Event Request is a mandatory opcode required by
specification (Figure 40, Section 5 in NVMe 1.2; Figure 41, Section 5
in NVMe 1.3). A simple way to deal with this in an emulator that
doesn't really want to use async events is to queue up the requests
and not do anything with them, and only complete them when the driver
aborts the command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1747393/+subscriptions
next prev parent reply other threads:[~2018-02-08 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 10:27 [Qemu-devel] [Bug 1747393] [NEW] nvme is missing support for NVME_ADM_CMD_ASYNC_EV_REQ Toomas Soome
2018-02-08 17:32 ` Toomas Soome [this message]
2021-04-21 6:24 ` [Bug 1747393] " Thomas Huth
2021-04-21 7:29 ` Klaus Jensen
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=151811112806.27805.4234071796130648960.launchpad@soybean.canonical.com \
--to=tsoome@me.com \
--cc=1747393@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).