From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-block@nongnu.org, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH] qapi: better document NVMe blockdev @device parameter
Date: Fri, 6 Dec 2019 08:51:15 -0600 [thread overview]
Message-ID: <fa41baea-5b86-192d-97ed-6f13caf2fdfa@redhat.com> (raw)
In-Reply-To: <20191206143811.3777524-1-berrange@redhat.com>
On 12/6/19 8:38 AM, Daniel P. Berrangé wrote:
> Mention that this is a PCI device address & give the format it is
> expected it. Also mention that it must be first unbound from any
maybe s/expected it/expecting/
> host kernel driver.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> qapi/block-core.json | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index 0cf68fea14..fcb52ec24f 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -2963,9 +2963,13 @@
> #
> # Driver specific block device options for the NVMe backend.
> #
> -# @device: controller address of the NVMe device.
> +# @device: PCI controller address of the NVMe device in
> +# format hhhh:bb:ss.f (host:bus:slot.function)
> # @namespace: namespace number of the device, starting from 1.
> #
> +# Note that the PCI @device must have been unbound from any host
> +# kernel driver before instructing QEMU to add the blockdev.
> +#
Reviewed-by: Eric Blake <eblake@redhat.com>
Doesn't affect code, but similarly no reason to hurry this into 4.2.
5.0 and qemu-stable (cc'd) is good enough.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-12-06 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 14:38 [PATCH] qapi: better document NVMe blockdev @device parameter Daniel P. Berrangé
2019-12-06 14:43 ` Stefan Hajnoczi
2019-12-06 14:51 ` Eric Blake [this message]
2019-12-06 14:53 ` Daniel P. Berrangé
2019-12-10 14:51 ` Kevin Wolf
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=fa41baea-5b86-192d-97ed-6f13caf2fdfa@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@redhat.com \
/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).