From: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
To: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, alex.williamson@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC 1/1] vfio/pci: Fix incorrect error message
Date: Tue, 25 Apr 2017 12:56:42 +0800 [thread overview]
Message-ID: <20170425045642.GG31848@bjsdjshi@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170425045201.71457-1-bjsdjshi@linux.vnet.ibm.com>
* Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> [2017-04-25 06:52:01 +0200]:
Hey Alex,
Please ignore the "RFC" tag in the subject. Sorry for the mistake.
> When the "No host device provided" error occurs, the hint message
> that starts with "Use -vfio-pci," makes no sense, since "-vfio-pci"
> is not a valid command line parameter.
>
> Correct this by replacing "-vfio-pci" with "-device vfio-pci".
>
> Signed-off-by: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
> ---
> hw/vfio/pci.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index 03a3d01..32aca77 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -2625,8 +2625,8 @@ static void vfio_realize(PCIDevice *pdev, Error **errp)
> if (!(~vdev->host.domain || ~vdev->host.bus ||
> ~vdev->host.slot || ~vdev->host.function)) {
> error_setg(errp, "No provided host device");
> - error_append_hint(errp, "Use -vfio-pci,host=DDDD:BB:DD.F "
> - "or -vfio-pci,sysfsdev=PATH_TO_DEVICE\n");
> + error_append_hint(errp, "Use -device vfio-pci,host=DDDD:BB:DD.F "
> + "or -device vfio-pci,sysfsdev=PATH_TO_DEVICE\n");
> return;
> }
> vdev->vbasedev.sysfsdev =
> --
> 2.10.2
>
--
Dong Jia Shi
next prev parent reply other threads:[~2017-04-25 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 4:52 [Qemu-devel] [PATCH RFC 1/1] vfio/pci: Fix incorrect error message Dong Jia Shi
2017-04-25 4:56 ` Dong Jia Shi [this message]
2017-04-26 8:06 ` Auger Eric
2017-04-26 9:07 ` Dong Jia Shi
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=20170425045642.GG31848@bjsdjshi@linux.vnet.ibm.com \
--to=bjsdjshi@linux.vnet.ibm.com \
--cc=alex.williamson@redhat.com \
--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).