[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <MWHPR03MB2669C98A17A4B450BB0BA72EBFB80@MWHPR03MB2669.namprd03.prod.outlook.com>
Date: Thu, 10 Nov 2016 07:16:22 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: Bjorn Helgaas <bhelgaas@...gle.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>
CC: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"Stephen Hemminger" <sthemmin@...rosoft.com>,
Jake Oshins <jakeo@...rosoft.com>,
"Hadden Hoppert" <haddenh@...rosoft.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"apw@...onical.com" <apw@...onical.com>,
"olaf@...fle.de" <olaf@...fle.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/3] PCI: hv: clean-up and 2 fixes to the hot-remove case
PATCH 1 is just a clean-up. There should be no functional change.
PATCH 2 and 3 are for device hot-remove case.
Currently the driver will stop working or even cause panic, if we do
hot add/remove quickly a few times. With the 2 patches, everything works
reliably in my tests now.
There can be still a potential issue with hot-remove when we unload
the driver at the same time. That would require more work of proper
synchronization among the 3 paths: the .probe/.remove, the channel callback,
and the offloaded hv_pci_devices_present()/hv_eject_device_work().
But for now, PATCH 2 and 3 do improve the situation a lot.
Dexuan Cui (3):
PCI: hv: use the correct buffer size in new_pcichild_device()
PCI: hv: fix hv_pci_remove() for hot-remove
PCI: hv: delete the device earlier from hbus->children for hot-remove
drivers/pci/host/pci-hyperv.c | 67 ++++++++++++++++++++++++++-----------------
1 file changed, 40 insertions(+), 27 deletions(-)
--
2.7.4
Powered by blists - more mailing lists