search for: davidhildenbrand

On 29.03.20 14:42, Michael S. Tsirkin wrote: > On Wed, Mar 11, 2020 at 06:14:12PM +0100, David Hildenbrand wrote: >> 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. > > I'd like to...

On 29.03.20 14:42, Michael S. Tsirkin wrote: > On Wed, Mar 11, 2020 at 06:14:12PM +0100, David Hildenbrand wrote: >> 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. > > I'd like to...

? 2020/6/5 ??6:05, David Hildenbrand ??: >> I guess I know what's happening here. In case we only have DMA memory >> when booting, we don't reserve swiotlb buffers. Once we hotplug memory >> and online ZONE_NORMAL, we don't have any swiotlb DMA bounce buffers to >> map such PFNs (total 0 (slots), used 0 (slots)). >> >> Can you try with

? 2020/6/5 ??6:05, David Hildenbrand ??: >> I guess I know what's happening here. In case we only have DMA memory >> when booting, we don't reserve swiotlb buffers. Once we hotplug memory >> and online ZONE_NORMAL, we don't have any swiotlb DMA bounce buffers to >> map such PFNs (total 0 (slots), used 0 (slots)). >> >> Can you try with

...ch #2) from virtio > folks. > > I'm planning to send a proper v1 (!RFC) once I have all necessary MM > acks. In the meanwhile, I will do more testing and minor reworks (e.g., > fix !CONFIG_NUMA compilation). Hi David, Thanks for your work! I am trying your https://github.com/davidhildenbrand/linux.git virtio-mem-v5 which works fine for me, but just a 'DMA error' happens when a vm start with less than 2GB memory, Do I missed sth? Thanks Alex (qemu) qom-set vm0 requested-size 1g (qemu) [ 26.560026] virtio_mem virtio0: plugged size: 0x0 [ 26.560648] virtio_mem virtio0: requ...

...ch #2) from virtio > folks. > > I'm planning to send a proper v1 (!RFC) once I have all necessary MM > acks. In the meanwhile, I will do more testing and minor reworks (e.g., > fix !CONFIG_NUMA compilation). Hi David, Thanks for your work! I am trying your https://github.com/davidhildenbrand/linux.git virtio-mem-v5 which works fine for me, but just a 'DMA error' happens when a vm start with less than 2GB memory, Do I missed sth? Thanks Alex (qemu) qom-set vm0 requested-size 1g (qemu) [ 26.560026] virtio_mem virtio0: plugged size: 0x0 [ 26.560648] virtio_mem virtio0: requ...

...v1 (!RFC) once I have all necessary MM >>> acks. In the meanwhile, I will do more testing and minor reworks (e.g., >>> fix !CONFIG_NUMA compilation). >> >> >> Hi David, >> >> Thanks for your work! >> >> I am trying your https://github.com/davidhildenbrand/linux.git virtio-mem-v5 >> which works fine for me, but just a 'DMA error' happens when a vm start with >> less than 2GB memory, Do I missed sth? > > Please use the virtio-mem-v4 branch for now, v5 is still under > construction (and might be scrapped completely if v4 g...

...v1 (!RFC) once I have all necessary MM >>> acks. In the meanwhile, I will do more testing and minor reworks (e.g., >>> fix !CONFIG_NUMA compilation). >> >> >> Hi David, >> >> Thanks for your work! >> >> I am trying your https://github.com/davidhildenbrand/linux.git virtio-mem-v5 >> which works fine for me, but just a 'DMA error' happens when a vm start with >> less than 2GB memory, Do I missed sth? > > Please use the virtio-mem-v4 branch for now, v5 is still under > construction (and might be scrapped completely if v4 g...

...; I am sharing for now only the linux driver side. The current code can be > found at [2]. The QEMU side is still heavily WIP, the current QEMU > prototype can be found at [3]. > > > [1] https://lists.gnu.org/archive/html/qemu-devel/2017-06/msg03870.html > [2] https://github.com/davidhildenbrand/linux/tree/virtio-mem > [3] https://github.com/davidhildenbrand/qemu/tree/virtio-mem > [4] https://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1698014.html > > David Hildenbrand (4): > ACPI: NUMA: export pxm_to_node > s390: mm: support removal of memory > s39...

On Thu, Dec 12, 2019 at 06:11:24PM +0100, David Hildenbrand wrote: > This series is based on latest linux-next. The patches are located at: > https://github.com/davidhildenbrand/linux.git virtio-mem-rfc-v4 Heya! Would there be by any chance a virtio-spec git tree somewhere? ..snip.. > -------------------------------------------------------------------------- > 5. Future work > -------------------------------------------------------------------------- > >...

...2020 at 11:15:18AM +0200, David Hildenbrand wrote: > On 29.03.20 14:42, Michael S. Tsirkin wrote: > > On Wed, Mar 11, 2020 at 06:14:12PM +0100, David Hildenbrand wrote: > >> 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. > &g...

...MM >>>> acks. In the meanwhile, I will do more testing and minor reworks (e.g., >>>> fix !CONFIG_NUMA compilation). >>> >>> >>> Hi David, >>> >>> Thanks for your work! >>> >>> I am trying your https://github.com/davidhildenbrand/linux.git virtio-mem-v5 >>> which works fine for me, but just a 'DMA error' happens when a vm start with >>> less than 2GB memory, Do I missed sth? >> >> Please use the virtio-mem-v4 branch for now, v5 is still under >> construction (and might be scrapped...

...reate proper ACPI tables that indicate hotpluggable memory. (I'll have >> to look into QEMU to figure out to always indicate hotpluggable memory >> that way). >> > > > That works too. Yes, better resolved in qemu, maybe. :) > You can checkout git at github.com:davidhildenbrand/qemu.git virtio-mem-v4 (prone to change before officially sent), which will create srat tables also if no "slots" parameter was defined (and no -numa config was specified). Your original example should work with that. -- Thanks, David / dhildenb

...'m planning to send a proper v1 (!RFC) once I have all necessary MM >> acks. In the meanwhile, I will do more testing and minor reworks (e.g., >> fix !CONFIG_NUMA compilation). > > > Hi David, > > Thanks for your work! > > I am trying your https://github.com/davidhildenbrand/linux.git virtio-mem-v5 > which works fine for me, but just a 'DMA error' happens when a vm start with > less than 2GB memory, Do I missed sth? Please use the virtio-mem-v4 branch for now, v5 is still under construction (and might be scrapped completely if v4 goes upstream as is). L...

On Thu, May 07, 2020 at 12:31:04PM +0200, David Hildenbrand wrote: > 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. Looks like you lost some acks, in particular I'd like to preserve Andrew Morton's...

On 02.03.20 14:49, David Hildenbrand wrote: > 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 materia...

...cially pc-i440fx-5.0? Both, hotplugging DIMMs and virtio-mem works for me with that QEMU machine just fine. What also seems to make it work with pc-i440fx-2.1, is giving the machine 4G of initial memory (-m 4g,slots=10,maxmem=5G). Cheers! > // start a QEMU that is get from https://github.com/davidhildenbrand/qemu/tree/virtio-mem-v2 and setup a file as a ide disk. > /home/teawater/qemu/qemu/x86_64-softmmu/qemu-system-x86_64 -machine pc-i440fx-2.1,accel=kvm,usb=off -cpu host -no-reboot -nographic -device ide-hd,drive=hd -drive if=none,id=hd,file=/home/teawater/old.img,format=raw -kernel /home/teawater...

...in this prototype. Basic migration works (not involving userfaultfd). Please, don't even try to review it (that's why I will also not attach any patches to this mail :) ), just use this as an inspiration what this could look like. You can find the latest hack at: QEMU: https://github.com/davidhildenbrand/qemu/tree/virtio-mem Kernel: https://github.com/davidhildenbrand/linux/tree/virtio-mem Use the kernel in the guest and make sure to compile the virtio-mem driver into the kernel (CONFIG_VIRTIO_MEM=y). A host kernel patch is contained to allow atomic resize of KVM memory regions, however it is pre...

...in this prototype. Basic migration works (not involving userfaultfd). Please, don't even try to review it (that's why I will also not attach any patches to this mail :) ), just use this as an inspiration what this could look like. You can find the latest hack at: QEMU: https://github.com/davidhildenbrand/qemu/tree/virtio-mem Kernel: https://github.com/davidhildenbrand/linux/tree/virtio-mem Use the kernel in the guest and make sure to compile the virtio-mem driver into the kernel (CONFIG_VIRTIO_MEM=y). A host kernel patch is contained to allow atomic resize of KVM memory regions, however it is pre...

...ation works (not involving userfaultfd). > > Please, don't even try to review it (that's why I will also not attach > any patches to this mail :) ), just use this as an inspiration what this > could look like. You can find the latest hack at: > > QEMU: https://github.com/davidhildenbrand/qemu/tree/virtio-mem > > Kernel: https://github.com/davidhildenbrand/linux/tree/virtio-mem > > Use the kernel in the guest and make sure to compile the virtio-mem > driver into the kernel (CONFIG_VIRTIO_MEM=y). A host kernel patch is > contained to allow atomic resize of KVM mem...