search for: out_unreg_mem

...99 1400 /* register callbacks */ 1401 vm->memory_notifier.notifier_call = virtio_mem_memory_notifier_cb; 1402 rc = register_memory_notifier(&vm->memory_notifier); 1403 if (rc) 1404 goto out_del_vq; 1405 rc = register_virtio_mem_device(vm); 1406 if (rc) 1407 goto out_unreg_mem; 1408 1409 virtio_device_ready(vdev); 1410 1411 /* trigger a config update to start processing the requested_size */ 1412 atomic_set(&vm->config_changed, 1); 1413 queue_work(system_freezable_wq, &vm->wq); 1414 1415 return 0; 1416 out_unreg_mem: 1417 unregi...

...97 1398 /* register callbacks */ 1399 vm->memory_notifier.notifier_call = virtio_mem_memory_notifier_cb; 1400 rc = register_memory_notifier(&vm->memory_notifier); 1401 if (rc) 1402 goto out_del_vq; 1403 rc = register_virtio_mem_device(vm); 1404 if (rc) 1405 goto out_unreg_mem; 1406 1407 virtio_device_ready(vdev); 1408 1409 /* trigger a config update to start processing the requested_size */ 1410 atomic_set(&vm->config_changed, 1); 1411 queue_work(system_freezable_wq, &vm->wq); 1412 1413 return 0; 1414 out_unreg_mem: 1415 unregi...

...97 1398 /* register callbacks */ 1399 vm->memory_notifier.notifier_call = virtio_mem_memory_notifier_cb; 1400 rc = register_memory_notifier(&vm->memory_notifier); 1401 if (rc) 1402 goto out_del_vq; 1403 rc = register_virtio_mem_device(vm); 1404 if (rc) 1405 goto out_unreg_mem; 1406 1407 virtio_device_ready(vdev); 1408 1409 /* trigger a config update to start processing the requested_size */ 1410 atomic_set(&vm->config_changed, 1); 1411 queue_work(system_freezable_wq, &vm->wq); 1412 1413 return 0; 1414 out_unreg_mem: 1415 unregi...

...irtio_mem_init(vm); + if (rc) + goto out_del_vq; + + /* register callbacks */ + vm->memory_notifier.notifier_call = virtio_mem_memory_notifier_cb; + rc = register_memory_notifier(&vm->memory_notifier); + if (rc) + goto out_del_vq; + rc = register_virtio_mem_device(vm); + if (rc) + goto out_unreg_mem; + + virtio_device_ready(vdev); + + /* trigger a config update to start processing the requested_size */ + atomic_set(&vm->config_changed, 1); + queue_work(system_freezable_wq, &vm->wq); + + return 0; +out_unreg_mem: + unregister_memory_notifier(&vm->memory_notifier); +out_del_...

This series is based on v5.7-rc4. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v4 This is basically a resend of v3 [1], now based on v5.7-rc4 and restested. One patch was reshuffled and two ACKs I missed to add were added. The rebase did not require any modifications to patches. Details about virtio-mem can be found in the cover letter of v2 [2]. A

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v3 Patch #1 - #10 where contained in v2 and only contain minor modifications (mostly smaller fixes). The remaining patches are new and contain smaller optimizations. Details about virtio-mem can be found in the cover letter of v2 [1]. A basic QEMU implementation was

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v3 Patch #1 - #10 where contained in v2 and only contain minor modifications (mostly smaller fixes). The remaining patches are new and contain smaller optimizations. Details about virtio-mem can be found in the cover letter of v2 [1]. A basic QEMU implementation was

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v2 I now have acks for all !virtio-mem changes. I'll be happy to get review feedback, testing reports, etc. for the virtio-mem changes. If there are no further comments, I guess this is good to go as a v1 soon. The basic idea of virtio-mem is to provide a

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-rfc-v4 The basic idea of virtio-mem is to provide a flexible, cross-architecture memory hot(un)plug solution that avoids many limitations imposed by existing technologies, architectures, and interfaces. More details can be found below and in linked material. This

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-rfc-v4 The basic idea of virtio-mem is to provide a flexible, cross-architecture memory hot(un)plug solution that avoids many limitations imposed by existing technologies, architectures, and interfaces. More details can be found below and in linked material. This

Long time no RFC! I finally had time to get the next version of the Linux driver side of virtio-mem into shape, incorporating ideas and feedback from previous discussions. This RFC is based on the series currently on the mm list: - [PATCH 0/3] Remove __online_page_set_limits() - [PATCH v1 0/3] mm/memory_hotplug: Export generic_online_page() - [PATCH v4 0/8] mm/memory_hotplug: Shrink zones before

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v1 The basic idea of virtio-mem is to provide a flexible, cross-architecture memory hot(un)plug solution that avoids many limitations imposed by existing technologies, architectures, and interfaces. More details can be found below and in linked material. It's

This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v1 The basic idea of virtio-mem is to provide a flexible, cross-architecture memory hot(un)plug solution that avoids many limitations imposed by existing technologies, architectures, and interfaces. More details can be found below and in linked material. It's