Displaying 7 results from an estimated 7 matches for "subsystem_register".
2020 Feb 13
1
[PATCH V2 3/5] vDPA: introduce vDPA bus
...e:
> > The 'class' is supposed to provide all the library functions to remove
> > this duplication. Instead of plugging the HW driver in via some bus
> > scheme every subsystem has its own 'ops' that the HW driver provides
> > to the subsystem's class via subsystem_register()
>
> Hmm I'm not familiar with subsystem_register. A grep didn't find it
> in the kernel either ...
I mean it is the registration function provided by the subsystem that
owns the class, for instance tpm_chip_register(),
ib_register_device(), register_netdev(), rtc_register_devic...
2020 Feb 13
4
[PATCH V2 3/5] vDPA: introduce vDPA bus
...s the subsystem core is
badly done wrong.
The 'class' is supposed to provide all the library functions to remove
this duplication. Instead of plugging the HW driver in via some bus
scheme every subsystem has its own 'ops' that the HW driver provides
to the subsystem's class via subsystem_register()
This is the *standard* pattern to use the driver core.
This is almost there, it just has this extra bus part to convey the HW
ops instead of directly.
> Instead, each device implement the same interface, and then
> vhost sits on top.
Sure, but plugging in via ops/etc not via a bus and a...
2020 Feb 13
4
[PATCH V2 3/5] vDPA: introduce vDPA bus
...s the subsystem core is
badly done wrong.
The 'class' is supposed to provide all the library functions to remove
this duplication. Instead of plugging the HW driver in via some bus
scheme every subsystem has its own 'ops' that the HW driver provides
to the subsystem's class via subsystem_register()
This is the *standard* pattern to use the driver core.
This is almost there, it just has this extra bus part to convey the HW
ops instead of directly.
> Instead, each device implement the same interface, and then
> vhost sits on top.
Sure, but plugging in via ops/etc not via a bus and a...
2020 Feb 13
0
[PATCH V2 3/5] vDPA: introduce vDPA bus
...Jason Gunthorpe wrote:
> The 'class' is supposed to provide all the library functions to remove
> this duplication. Instead of plugging the HW driver in via some bus
> scheme every subsystem has its own 'ops' that the HW driver provides
> to the subsystem's class via subsystem_register()
Hmm I'm not familiar with subsystem_register. A grep didn't find it
in the kernel either ...
--
MST
2007 Jun 20
0
[PATCH] linux-2.6.18: utilize SYS_HYPERVISOR config option
...n 0;
}
-struct sysfs_ops hyp_sysfs_ops = {
+static struct sysfs_ops hyp_sysfs_ops = {
.show = hyp_sysfs_show,
.store = hyp_sysfs_store,
};
@@ -52,8 +50,7 @@ static int __init hypervisor_subsys_init
return -ENODEV;
hypervisor_subsys.kset.kobj.ktype = &hyp_sysfs_kobj_type;
- return subsystem_register(&hypervisor_subsys);
+ return 0;
}
device_initcall(hypervisor_subsys_init);
-EXPORT_SYMBOL_GPL(hypervisor_subsys);
Index: head-2007-05-31/include/xen/hypervisor_sysfs.h
===================================================================
--- head-2007-05-31.orig/include/xen/hypervisor_sysfs....
2020 Feb 13
4
[PATCH V2 3/5] vDPA: introduce vDPA bus
On Thu, Feb 13, 2020 at 10:58:44PM +0800, Jason Wang wrote:
>
> On 2020/2/13 ??9:41, Jason Gunthorpe wrote:
> > On Thu, Feb 13, 2020 at 11:34:10AM +0800, Jason Wang wrote:
> >
> > > > You have dev, type or
> > > > class to choose from. Type is rarely used and doesn't seem to be used
> > > > by vdpa, so class seems the right choice
>
2020 Feb 13
4
[PATCH V2 3/5] vDPA: introduce vDPA bus
On Thu, Feb 13, 2020 at 10:58:44PM +0800, Jason Wang wrote:
>
> On 2020/2/13 ??9:41, Jason Gunthorpe wrote:
> > On Thu, Feb 13, 2020 at 11:34:10AM +0800, Jason Wang wrote:
> >
> > > > You have dev, type or
> > > > class to choose from. Type is rarely used and doesn't seem to be used
> > > > by vdpa, so class seems the right choice
>