[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ed4057aa-d69e-e803-752b-c007ab4e707d@fensystems.co.uk>
Date: Mon, 17 May 2021 22:51:38 +0100
From: Michael Brown <mbrown@...systems.co.uk>
To: Marek Marczykowski-Górecki
<marmarek@...isiblethingslab.com>,
"Durrant, Paul" <pdurrant@...zon.co.uk>
Cc: "paul@....org" <paul@....org>,
"xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"wei.liu@...nel.org" <wei.liu@...nel.org>,
Ian Jackson <iwj@...project.org>, Wei Liu <wl@....org>,
Anthony PERARD <anthony.perard@...rix.com>
Subject: Re: [PATCH] xen-netback: Check for hotplug-status existence before
watching
On 17/05/2021 22:43, Marek Marczykowski-Górecki wrote:
> In any case, the issue is not calling the hotplug script, responsible
> for configuring newly created vif interface. Not kernel waiting for it.
> So, I think both commits should still be reverted.
Did you also test the ability for a domU to have the netfront driver
reloaded? (That should be roughly equivalent to my original test
scenario comprising the iPXE netfront driver used to boot a kernel that
then loads the Linux netfront driver.)
Michael
Powered by blists - more mailing lists