From: Thomas Monjalon <thomas@monjalon.net>
To: "Huang, Wei" <wei.huang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Xu, Rosen" <rosen.xu@intel.com>,
"Zhang, Tianfei" <tianfei.zhang@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: Re: [PATCH v1] raw/ifpga: remove virtual device unplug operation
Date: Tue, 21 Mar 2023 11:30:19 +0100 [thread overview]
Message-ID: <2637984.KRxA6XjA2N@thomas> (raw)
In-Reply-To: <DM6PR11MB35302CEFBD9FD904202E18C1EF819@DM6PR11MB3530.namprd11.prod.outlook.com>
21/03/2023 09:41, Huang, Wei:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 21/03/2023 01:11, Huang, Wei:
> > > From: Thomas Monjalon <thomas@monjalon.net>
> > > > 16/03/2023 21:44, Wei Huang:
> > > > > VDEV bus has implemented cleanup() function to perform cleanup for
> > > > > devices on the bus during eal_cleanup(), so there is no need for
> > > > > ifpga driver to record virtual devices and unplug them.
> > > >
> > > > Why no need?
> > > > If the application wants to explicitly remove a device, what happens?
> > > >
> > > >
> > > EAL will output an error information "Cannot find plugged device (%s)".
> >
> > It does not look what we expect.
> >
> Let me clear it.
> With this patch, no error information will be outputted.
> Without this patch, error information will be outputted.
> Because bus cleanup action will unplug virtual device,
> then ifpga PMD unplug the virtual device which is already be cleanup,
Why ipfga unplug the device after the bus cleanup?
I'm not following.
> bus->find_device() returns NULL,
> EAL output "Cannot find plugged device (%s)\n" at line 302 in eal_common_dev.c
Anyway, the good answer is not to completely remove the "remove" operation.
next prev parent reply other threads:[~2023-03-21 10:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 20:44 Wei Huang
2023-03-20 6:51 ` Xu, Rosen
2023-03-20 12:58 ` Zhang, Qi Z
2023-03-20 13:00 ` Zhang, Qi Z
2023-03-20 16:06 ` Thomas Monjalon
2023-03-21 0:11 ` Huang, Wei
2023-03-21 8:14 ` Thomas Monjalon
2023-03-21 8:41 ` Huang, Wei
2023-03-21 10:30 ` Thomas Monjalon [this message]
2023-03-22 1:26 ` Huang, Wei
2023-03-22 11:54 ` Thomas Monjalon
2023-03-23 3:26 ` Huang, Wei
2023-03-23 8:52 ` Thomas Monjalon
2023-03-24 1:27 ` Huang, Wei
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=2637984.KRxA6XjA2N@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=rosen.xu@intel.com \
--cc=stable@dpdk.org \
--cc=tianfei.zhang@intel.com \
--cc=wei.huang@intel.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).