From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: David Marchand <david.marchand@redhat.com>, dev@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
Chenbo Xia <chenbox@nvidia.com>,
Nipun Gupta <nipun.gupta@amd.com>
Subject: Re: [PATCH 2/2] bus/pci: enhance hotplug for VFIO bound devices
Date: Tue, 17 Sep 2024 10:57:35 +0200 [thread overview]
Message-ID: <65946c51-d684-47af-b80f-05a27d17e83c@redhat.com> (raw)
In-Reply-To: <20240916123044.2692301-2-david.marchand@redhat.com>
On 9/16/24 14:30, David Marchand wrote:
> VFIO modules may get loaded/initialized after DPDK initialized (like when
> starting an application without knowing which devices will be used, and
> whether their drivers require VFIO).
>
> Retry enabling VFIO if not available.
> This way, it is not required to restart the DPDK application anymore.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> drivers/bus/pci/linux/pci_vfio.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/bus/pci/linux/pci_vfio.c b/drivers/bus/pci/linux/pci_vfio.c
> index adc34a5c51..5317170231 100644
> --- a/drivers/bus/pci/linux/pci_vfio.c
> +++ b/drivers/bus/pci/linux/pci_vfio.c
> @@ -1319,6 +1319,12 @@ pci_vfio_mmio_write(const struct rte_pci_device *dev, int bar,
> int
> pci_vfio_is_enabled(void)
> {
> - return rte_vfio_is_enabled("vfio_pci");
> + int status = rte_vfio_is_enabled("vfio_pci");
> +
> + if (!status) {
> + rte_vfio_enable("vfio");
> + status = rte_vfio_is_enabled("vfio_pci");
> + }
> + return status;
> }
> #endif
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Also wondering if it could be considered a fix.
Thanks,
Maxime
next prev parent reply other threads:[~2024-09-17 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 12:30 [PATCH 1/2] eal/linux: fix VFIO hotplug with multiprocess David Marchand
2024-09-16 12:30 ` [PATCH 2/2] bus/pci: enhance hotplug for VFIO bound devices David Marchand
2024-09-17 8:57 ` Maxime Coquelin [this message]
2024-09-17 8:20 ` [PATCH 1/2] eal/linux: fix VFIO hotplug with multiprocess Maxime Coquelin
2024-10-02 18:31 ` David Marchand
2024-10-03 8:25 ` Kevin Traynor
2024-10-14 18:58 ` David Marchand
2024-10-04 14:34 ` David Marchand
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=65946c51-d684-47af-b80f-05a27d17e83c@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nipun.gupta@amd.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).