On Fri, 29 Sep 2017, Sinan Kaya wrote:
On 9/28/2017 7:46 PM, Govindarajulu Varadarajan wrote:
How about releasing the device_lock here on CPU0?>
pci_device_add() is called by driver's pci probe function. device_lock(dev)
should be held before calling pci driver probe function.
I see. The go
On 9/28/2017 7:46 PM, Govindarajulu Varadarajan wrote:
>> How about releasing the device_lock here on CPU0?>
>
> pci_device_add() is called by driver's pci probe function. device_lock(dev)
> should be held before calling pci driver probe function.
I see. The goal of the lock held here is to prote
On Thu, 28 Sep 2017, Sinan Kaya wrote:
On 9/27/2017 5:42 PM, Govindarajulu Varadarajan wrote:
CPU0CPU1
-
__driver_attach()
device_lock(&dev->mutex) <--- device mutex lock here
driver_probe_de
On 9/27/2017 5:42 PM, Govindarajulu Varadarajan wrote:
> CPU0 CPU1
> -
> __driver_attach()
> device_lock(&dev->mutex) <--- device mutex lock here
> driver_probe_device()
> pci_enable_sriov()
> pci_i
CPU0CPU1
-
__driver_attach()
device_lock(&dev->mutex) <--- device mutex lock here
driver_probe_device()
pci_enable_sriov()
pci_iov_add_virtfn()
pci_device_add()
5 matches
Mail list logo