From: Thomas Monjalon <thomas@monjalon.net>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] dev: fix virtual dev attach
Date: Mon, 31 Jul 2017 15:20:29 +0200 [thread overview]
Message-ID: <3447349.fNn8M4kDGr@xps> (raw)
In-Reply-To: <032453ede0e0c6d5464bd9d53a45b48cf4d229db.1501505748.git.gaetan.rivet@6wind.com>
31/07/2017 14:58, Gaetan Rivet:
> Checking against error values returned by rte_eal_hotplug_add is
> inelegant and prone to mistakes. Additionally, the failed PCI probe
> prints a useless error that would throw off unsuspecting users:
>
> ERROR: failed to parse device "pci:net_ring0"
>
> This error is printed when attempting to probe a virtual device first
> with the PCI bus (here, a net_ring0 device), which will inevitably fail.
>
> Use the relevant functions to infer the intended bus. The limitation to
> PCI or vdev device is kept for strict API compatibility. Thus the PCI
> probe attempt is avoided and the right function is directly called.
>
> Fixes: 1c35f666df07 ("dev: fix attach proceeding with vdev on PCI
> success")
>
> Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
Applied with additional explanation from v1, thanks:
dev: fix vdev attach after PCI mismatch
If the device is a vdev, the parsing for PCI will fail with -EFAULT,
and will not try to check for a vdev.
prev parent reply other threads:[~2017-07-31 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 10:57 [dpdk-dev] [PATCH] " Gaetan Rivet
2017-07-31 10:59 ` [dpdk-dev] [PATCH v2] " Gaetan Rivet
2017-07-31 12:58 ` [dpdk-dev] [PATCH v3] " Gaetan Rivet
2017-07-31 13:20 ` Thomas Monjalon [this message]
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=3447349.fNn8M4kDGr@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.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).