On 1/18/2018 6:00 AM, Thomas Monjalon wrote:
15/01/2018 11:48, Jeff Guo:
+enum rte_dev_event_subsystem {
+ RTE_DEV_EVENT_SUBSYSTEM_UIO,
+ RTE_DEV_EVENT_SUBSYSTEM_VFIO,
+ RTE_DEV_EVENT_SUBSYSTEM_PCI,
+ RTE_DEV_EVENT_SUBSYSTEM_MAX
+};
I still don't understand this classi
15/01/2018 11:48, Jeff Guo:
> +enum rte_dev_event_subsystem {
> + RTE_DEV_EVENT_SUBSYSTEM_UIO,
> + RTE_DEV_EVENT_SUBSYSTEM_VFIO,
> + RTE_DEV_EVENT_SUBSYSTEM_PCI,
> + RTE_DEV_EVENT_SUBSYSTEM_MAX
> +};
I still don't understand this classification, mixing PCI and VFIO
at the s
In order to handle the uevent which have been detected from the kernel
side, add uevent process function, let hot plug event to be example to
show uevent mechanism how to pass the uevent and process the uevent.
About uevent passing and processing, add below functions in linux eal
dev layer. FreeBS
3 matches
Mail list logo