On 7/11/2018 10:46 AM, Jeff Guo wrote:
On 7/11/2018 5:52 AM, Stephen Hemminger wrote:
On Tue, 10 Jul 2018 19:03:27 +0800
Jeff Guo wrote:
When hotplug out device, the device resource will be released in
kernel.
The fd sys file will disappear, and the irq will be released. At
this time,
i
On 7/11/2018 5:48 AM, Stephen Hemminger wrote:
On Tue, 10 Jul 2018 19:03:27 +0800
Jeff Guo wrote:
+/* uio pci device state */
+enum rte_udev_state {
+ RTE_UDEV_PROBED,
+ RTE_UDEV_OPENNED,
+ RTE_UDEV_RELEASED,
+ RTE_UDEV_REMOVED,
+};
+
The states here are a little
On 7/11/2018 5:52 AM, Stephen Hemminger wrote:
On Tue, 10 Jul 2018 19:03:27 +0800
Jeff Guo wrote:
When hotplug out device, the device resource will be released in kernel.
The fd sys file will disappear, and the irq will be released. At this time,
if igb uio driver still try to release this
On Tue, 10 Jul 2018 19:03:27 +0800
Jeff Guo wrote:
> When hotplug out device, the device resource will be released in kernel.
> The fd sys file will disappear, and the irq will be released. At this time,
> if igb uio driver still try to release this resource, it will cause kernel
> crash. On the
On Tue, 10 Jul 2018 19:03:27 +0800
Jeff Guo wrote:
>
> +/* uio pci device state */
> +enum rte_udev_state {
> + RTE_UDEV_PROBED,
> + RTE_UDEV_OPENNED,
> + RTE_UDEV_RELEASED,
> + RTE_UDEV_REMOVED,
> +};
> +
The states here are a little confusing. especially since pci_release
see
When hotplug out device, the device resource will be released in kernel.
The fd sys file will disappear, and the irq will be released. At this time,
if igb uio driver still try to release this resource, it will cause kernel
crash. On the other hand, interrupt disabling do not automatically be
proce
6 matches
Mail list logo
