search for: virtio_mmio_init

Displaying 20 results from an estimated 25 matches for "virtio_mmio_init".

2017 Dec 13
2
[PATCHv2] virtio_mmio: fix devm cleanup
...t; > [ 3.717645] bus_for_each_dev+0x14c/0x1f0 > > [ 3.728633] driver_attach+0x48/0x78 > > [ 3.740249] bus_add_driver+0x26c/0x5b8 > > [ 3.752248] driver_register+0x16c/0x398 > > [ 3.757211] __platform_driver_register+0xd8/0x128 > > [ 3.770860] virtio_mmio_init+0x1c/0x24 > > [ 3.782671] do_one_initcall+0xe0/0x398 > > [ 3.791890] kernel_init_freeable+0x594/0x660 > > [ 3.798514] kernel_init+0x18/0x190 > > [ 3.810220] ret_from_fork+0x10/0x18 > > > > To fix this, we can simply rip out the explicit cleanup t...
2017 Dec 13
2
[PATCHv2] virtio_mmio: fix devm cleanup
...t; > [ 3.717645] bus_for_each_dev+0x14c/0x1f0 > > [ 3.728633] driver_attach+0x48/0x78 > > [ 3.740249] bus_add_driver+0x26c/0x5b8 > > [ 3.752248] driver_register+0x16c/0x398 > > [ 3.757211] __platform_driver_register+0xd8/0x128 > > [ 3.770860] virtio_mmio_init+0x1c/0x24 > > [ 3.782671] do_one_initcall+0xe0/0x398 > > [ 3.791890] kernel_init_freeable+0x594/0x660 > > [ 3.798514] kernel_init+0x18/0x190 > > [ 3.810220] ret_from_fork+0x10/0x18 > > > > To fix this, we can simply rip out the explicit cleanup t...
2017 Dec 12
2
[PATCH] virtio_mmio: fix devm cleanup
...e+0x250/0x828 [ 3.706187] __driver_attach+0x190/0x210 [ 3.717645] bus_for_each_dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure will do for us when our probe fu...
2017 Dec 12
2
[PATCH] virtio_mmio: fix devm cleanup
...e+0x250/0x828 [ 3.706187] __driver_attach+0x190/0x210 [ 3.717645] bus_for_each_dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure will do for us when our probe fu...
2017 Dec 12
4
[PATCHv2] virtio_mmio: fix devm cleanup
...e+0x250/0x828 [ 3.706187] __driver_attach+0x190/0x210 [ 3.717645] bus_for_each_dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure will do for us when our probe fu...
2017 Dec 12
4
[PATCHv2] virtio_mmio: fix devm cleanup
...e+0x250/0x828 [ 3.706187] __driver_attach+0x190/0x210 [ 3.717645] bus_for_each_dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure will do for us when our probe fu...
2012 May 09
1
[PATCH] virtio-mmio: Devices parameter parsing
...cmdline_device); + device_unregister(&vm_cmdline_parent); + vm_cmdline_parent_registered = 0; + } +} + +#else + +static void vm_unregister_cmdline_devices(void) +{ +} + +#endif + /* Platform driver */ static struct of_device_id virtio_mmio_match[] = { @@ -475,6 +637,7 @@ static int __init virtio_mmio_init(void) static void __exit virtio_mmio_exit(void) { platform_driver_unregister(&virtio_mmio_driver); + vm_unregister_cmdline_devices(); } module_init(virtio_mmio_init); -- 1.7.5.4
2012 May 09
1
[PATCH] virtio-mmio: Devices parameter parsing
...cmdline_device); + device_unregister(&vm_cmdline_parent); + vm_cmdline_parent_registered = 0; + } +} + +#else + +static void vm_unregister_cmdline_devices(void) +{ +} + +#endif + /* Platform driver */ static struct of_device_id virtio_mmio_match[] = { @@ -475,6 +637,7 @@ static int __init virtio_mmio_init(void) static void __exit virtio_mmio_exit(void) { platform_driver_unregister(&virtio_mmio_driver); + vm_unregister_cmdline_devices(); } module_init(virtio_mmio_init); -- 1.7.5.4
2012 Apr 07
0
[PATCH 05/14] kvm tools: Add virtio-mmio support
...ruct virtio_mmio_ioevent_param ioeventfds[VIRTIO_MMIO_MAX_VQ]; +}; + +int virtio_mmio_signal_vq(struct kvm *kvm, struct virtio_device *vdev, u32 vq); +int virtio_mmio_signal_config(struct kvm *kvm, struct virtio_device *vdev); +int virtio_mmio_exit(struct kvm *kvm, struct virtio_device *vdev); +int virtio_mmio_init(struct kvm *kvm, void *dev, struct virtio_device *vdev, + int device_id, int subsys_id, int class); +#endif diff --git a/tools/kvm/virtio/mmio.c b/tools/kvm/virtio/mmio.c new file mode 100644 index 0000000..8319954 --- /dev/null +++ b/tools/kvm/virtio/mmio.c @@ -0,0 +1,256 @@ +#include &quot...
2012 Apr 07
0
[PATCH 05/14] kvm tools: Add virtio-mmio support
...ruct virtio_mmio_ioevent_param ioeventfds[VIRTIO_MMIO_MAX_VQ]; +}; + +int virtio_mmio_signal_vq(struct kvm *kvm, struct virtio_device *vdev, u32 vq); +int virtio_mmio_signal_config(struct kvm *kvm, struct virtio_device *vdev); +int virtio_mmio_exit(struct kvm *kvm, struct virtio_device *vdev); +int virtio_mmio_init(struct kvm *kvm, void *dev, struct virtio_device *vdev, + int device_id, int subsys_id, int class); +#endif diff --git a/tools/kvm/virtio/mmio.c b/tools/kvm/virtio/mmio.c new file mode 100644 index 0000000..8319954 --- /dev/null +++ b/tools/kvm/virtio/mmio.c @@ -0,0 +1,256 @@ +#include &quot...
2017 Dec 12
0
[PATCHv2] virtio_mmio: fix devm cleanup
...__driver_attach+0x190/0x210 > [ 3.717645] bus_for_each_dev+0x14c/0x1f0 > [ 3.728633] driver_attach+0x48/0x78 > [ 3.740249] bus_add_driver+0x26c/0x5b8 > [ 3.752248] driver_register+0x16c/0x398 > [ 3.757211] __platform_driver_register+0xd8/0x128 > [ 3.770860] virtio_mmio_init+0x1c/0x24 > [ 3.782671] do_one_initcall+0xe0/0x398 > [ 3.791890] kernel_init_freeable+0x594/0x660 > [ 3.798514] kernel_init+0x18/0x190 > [ 3.810220] ret_from_fork+0x10/0x18 > > To fix this, we can simply rip out the explicit cleanup that the devm > infrastructu...
2023 Sep 06
0
[PATCH] virtio-mmio: fix memory leak of vm_dev
...t;] bus_for_each_dev+0x74/0xd4 [<0000000026582009>] driver_attach+0x24/0x30 [<000000003e6b0968>] bus_add_driver+0xe4/0x1e8 [<000000009e7b5554>] driver_register+0x60/0x128 [<00000000d1f180b4>] __platform_driver_register+0x28/0x34 [<0000000097a0072e>] virtio_mmio_init+0x1c/0x28 [<00000000b3340a88>] do_one_initcall+0x6c/0x1b0 [<0000000048f4ff06>] kernel_init_freeable+0x1bc/0x284 > diff --git a/drivers/virtio/virtio_mmio.c b/drivers/virtio/virtio_mmio.c > index 97760f611295..b2a48d07e973 100644 > --- a/drivers/virtio/virtio_mmio.c &gt...
2017 Dec 14
0
[PATCHv2] virtio_mmio: fix devm cleanup
...us_for_each_dev+0x14c/0x1f0 > > > [ 3.728633] driver_attach+0x48/0x78 > > > [ 3.740249] bus_add_driver+0x26c/0x5b8 > > > [ 3.752248] driver_register+0x16c/0x398 > > > [ 3.757211] __platform_driver_register+0xd8/0x128 > > > [ 3.770860] virtio_mmio_init+0x1c/0x24 > > > [ 3.782671] do_one_initcall+0xe0/0x398 > > > [ 3.791890] kernel_init_freeable+0x594/0x660 > > > [ 3.798514] kernel_init+0x18/0x190 > > > [ 3.810220] ret_from_fork+0x10/0x18 > > > > > > To fix this, we can simply...
2017 Dec 12
2
[PATCH] virtio_mmio: fix devm cleanup
...t; > [ 3.717645] bus_for_each_dev+0x14c/0x1f0 > > [ 3.728633] driver_attach+0x48/0x78 > > [ 3.740249] bus_add_driver+0x26c/0x5b8 > > [ 3.752248] driver_register+0x16c/0x398 > > [ 3.757211] __platform_driver_register+0xd8/0x128 > > [ 3.770860] virtio_mmio_init+0x1c/0x24 > > [ 3.782671] do_one_initcall+0xe0/0x398 > > [ 3.791890] kernel_init_freeable+0x594/0x660 > > [ 3.798514] kernel_init+0x18/0x190 > > [ 3.810220] ret_from_fork+0x10/0x18 > > Oops. > > > To fix this, we can simply rip out the explic...
2017 Dec 12
2
[PATCH] virtio_mmio: fix devm cleanup
...t; > [ 3.717645] bus_for_each_dev+0x14c/0x1f0 > > [ 3.728633] driver_attach+0x48/0x78 > > [ 3.740249] bus_add_driver+0x26c/0x5b8 > > [ 3.752248] driver_register+0x16c/0x398 > > [ 3.757211] __platform_driver_register+0xd8/0x128 > > [ 3.770860] virtio_mmio_init+0x1c/0x24 > > [ 3.782671] do_one_initcall+0xe0/0x398 > > [ 3.791890] kernel_init_freeable+0x594/0x660 > > [ 3.798514] kernel_init+0x18/0x190 > > [ 3.810220] ret_from_fork+0x10/0x18 > > Oops. > > > To fix this, we can simply rip out the explic...
2017 Dec 12
0
[PATCH] virtio_mmio: fix devm cleanup
...__driver_attach+0x190/0x210 > [ 3.717645] bus_for_each_dev+0x14c/0x1f0 > [ 3.728633] driver_attach+0x48/0x78 > [ 3.740249] bus_add_driver+0x26c/0x5b8 > [ 3.752248] driver_register+0x16c/0x398 > [ 3.757211] __platform_driver_register+0xd8/0x128 > [ 3.770860] virtio_mmio_init+0x1c/0x24 > [ 3.782671] do_one_initcall+0xe0/0x398 > [ 3.791890] kernel_init_freeable+0x594/0x660 > [ 3.798514] kernel_init+0x18/0x190 > [ 3.810220] ret_from_fork+0x10/0x18 > Oops. > To fix this, we can simply rip out the explicit cleanup that the devm > infr...
2017 Dec 12
0
[PATCHv2] virtio_mmio: fix devm cleanup
...__driver_attach+0x190/0x210 > [ 3.717645] bus_for_each_dev+0x14c/0x1f0 > [ 3.728633] driver_attach+0x48/0x78 > [ 3.740249] bus_add_driver+0x26c/0x5b8 > [ 3.752248] driver_register+0x16c/0x398 > [ 3.757211] __platform_driver_register+0xd8/0x128 > [ 3.770860] virtio_mmio_init+0x1c/0x24 > [ 3.782671] do_one_initcall+0xe0/0x398 > [ 3.791890] kernel_init_freeable+0x594/0x660 > [ 3.798514] kernel_init+0x18/0x190 > [ 3.810220] ret_from_fork+0x10/0x18 > > To fix this, we can simply rip out the explicit cleanup that the devm > infrastructur...
2011 Nov 15
1
[PATCH] virtio-mmio: Devices parameter parsing
...register_cmdline_devices(void) +{ + return 0; +} + +static void virtio_mmio_unregister_cmdline_devices(void) +{ +} + +#endif + /* Platform driver */ static struct of_device_id virtio_mmio_match[] = { @@ -463,11 +627,15 @@ static struct platform_driver virtio_mmio_driver = { static int __init virtio_mmio_init(void) { - return platform_driver_register(&virtio_mmio_driver); + int err = virtio_mmio_register_cmdline_devices(); + + return err ? err : platform_driver_register(&virtio_mmio_driver); } static void __exit virtio_mmio_exit(void) { + virtio_mmio_unregister_cmdline_devices(); + platf...
2011 Nov 15
1
[PATCH] virtio-mmio: Devices parameter parsing
...register_cmdline_devices(void) +{ + return 0; +} + +static void virtio_mmio_unregister_cmdline_devices(void) +{ +} + +#endif + /* Platform driver */ static struct of_device_id virtio_mmio_match[] = { @@ -463,11 +627,15 @@ static struct platform_driver virtio_mmio_driver = { static int __init virtio_mmio_init(void) { - return platform_driver_register(&virtio_mmio_driver); + int err = virtio_mmio_register_cmdline_devices(); + + return err ? err : platform_driver_register(&virtio_mmio_driver); } static void __exit virtio_mmio_exit(void) { + virtio_mmio_unregister_cmdline_devices(); + platf...
2011 Oct 27
1
[PATCH v3] virtio: Add platform bus driver for memory mapped virtio device
On Mon, 2011-10-24 at 03:33 +0100, Rusty Russell wrote: > No, that's it I think. Please send a diff for the documentation, since > I'm updating the LyX master and I've already applied your previous > version. Here it goes (below). Also do you think you would be able to merge the driver (corresponding v4 patch follows) in the 3.2 merge window that seems to have just opened?