search for: host_resp

...1371 1372 static int virtio_mem_probe(struct virtio_device *vdev) 1373 { 1374 struct virtio_mem *vm; 1375 int rc = -EINVAL; 1376 1377 vdev->priv = vm = kzalloc(sizeof(*vm), GFP_KERNEL); 1378 if (!vm) 1379 return -ENOMEM; 1380 1381 init_waitqueue_head(&vm->host_resp); 1382 vm->vdev = vdev; 1383 INIT_WORK(&vm->wq, virtio_mem_run_wq); 1384 mutex_init(&vm->hotplug_mutex); 1385 INIT_LIST_HEAD(&vm->next); 1386 spin_lock_init(&vm->removal_lock); 1387 hrtimer_init(&vm->retry_timer, CLOCK_MONOTONIC, HRTIMER_MODE_...

...1369 1370 static int virtio_mem_probe(struct virtio_device *vdev) 1371 { 1372 struct virtio_mem *vm; 1373 int rc = -EINVAL; 1374 > 1375 vdev->priv = vm = kzalloc(sizeof(*vm), GFP_KERNEL); 1376 if (!vm) 1377 return -ENOMEM; 1378 1379 init_waitqueue_head(&vm->host_resp); 1380 vm->vdev = vdev; 1381 INIT_WORK(&vm->wq, virtio_mem_run_wq); 1382 mutex_init(&vm->hotplug_mutex); 1383 INIT_LIST_HEAD(&vm->next); 1384 spin_lock_init(&vm->removal_lock); 1385 hrtimer_init(&vm->retry_timer, CLOCK_MONOTONIC, HRTIMER_MODE_...

...1369 1370 static int virtio_mem_probe(struct virtio_device *vdev) 1371 { 1372 struct virtio_mem *vm; 1373 int rc = -EINVAL; 1374 > 1375 vdev->priv = vm = kzalloc(sizeof(*vm), GFP_KERNEL); 1376 if (!vm) 1377 return -ENOMEM; 1378 1379 init_waitqueue_head(&vm->host_resp); 1380 vm->vdev = vdev; 1381 INIT_WORK(&vm->wq, virtio_mem_run_wq); 1382 mutex_init(&vm->hotplug_mutex); 1383 INIT_LIST_HEAD(&vm->next); 1384 spin_lock_init(&vm->removal_lock); 1385 hrtimer_init(&vm->retry_timer, CLOCK_MONOTONIC, HRTIMER_MODE_...

...ing up. */ + bool unplug_all_required; + + /* Workqueue that processes the plug/unplug requests. */ + struct work_struct wq; + atomic_t config_changed; + + /* Virtqueue for guest->host requests. */ + struct virtqueue *vq; + + /* Wait for a host response to a guest request. */ + wait_queue_head_t host_resp; + + /* Space for one guest request and the host response. */ + struct virtio_mem_req req; + struct virtio_mem_resp resp; + + /* The current size of the device. */ + uint64_t plugged_size; + /* The requested size of the device. */ + uint64_t requested_size; + + /* The device block size (for communi...

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-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

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

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