From: Stephen Hemminger <stephen@networkplumber.org>
To: Huisong Li <lihuisong@huawei.com>
Cc: <dev@dpdk.org>, <andrew.rybchenko@oktetlabs.ru>,
<thomas@monjalon.net>, <ferruh.yigit@xilinx.com>,
<huangdaode@huawei.com>, <liudongdong3@huawei.com>
Subject: Re: [PATCH] usertools: fix bind failure from dpdk to kernel
Date: Fri, 5 Aug 2022 08:35:29 -0700 [thread overview]
Message-ID: <20220805083529.5ca3233e@hermes.local> (raw)
In-Reply-To: <20220805031022.9795-1-lihuisong@huawei.com>
On Fri, 5 Aug 2022 11:10:22 +0800
Huisong Li <lihuisong@huawei.com> wrote:
> Currently, the steps for binding device from dpdk driver to kernel
> driver is as follows:
> echo $BDF > /sys/bus/pci/drivers/vfio-pci/unbind
> echo $BDF > /sys/bus/pci/drivers/$kernel_driver/bind
>
> This steps cannot bind device from dpdk driver to kernel driver on
> platform with kernel 5.19. The 'driver_override' must be specify
> kernel driver before binding device to kernel driver.
>
> Fixes: 720b7a058260 ("usertools: fix device binding with kernel tools")
> Cc: stable@dpdk.org
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
Not sure exactly what you did and why.
The patch seems to just remove the check that the driver
is in the set of dpdk_drivers.
next prev parent reply other threads:[~2022-08-05 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 3:10 Huisong Li
2022-08-05 15:35 ` Stephen Hemminger [this message]
2022-08-09 11:44 ` lihuisong (C)
2022-08-09 17:58 ` Stephen Hemminger
2022-08-10 6:02 ` Krzysztof Kozlowski
2022-08-10 13:50 ` Stephen Hemminger
2022-08-10 5:59 ` Krzysztof Kozlowski
2022-08-10 13:49 ` Stephen Hemminger
2022-08-11 2:10 ` lihuisong (C)
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=20220805083529.5ca3233e@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=huangdaode@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=thomas@monjalon.net \
/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).