> Am 18.10.2020 um 14:50 schrieb Wei Yang <[email protected]>: > > On Mon, Oct 12, 2020 at 02:52:54PM +0200, David Hildenbrand wrote: >> virtio-mem currently only supports device block sizes that span at most >> a single Linux memory block. For example, gigantic pages in the hypervisor >> result on x86-64 in a device block size of 1 GiB - when the Linux memory >> block size is 128 MiB, we cannot support such devices (we fail loading the >> driver). Of course, we want to support any device block size in any Linux >> VM. >> >> Bigger device block sizes will become especially important once supporting >> VFIO in QEMU - each device block has to be mapped separately, and the >> maximum number of mappings for VFIO is 64k. So we usually want blocks in >> the gigabyte range when wanting to grow the VM big. >> >> This series: >> - Performs some cleanups >> - Factors out existing Sub Block Mode (SBM) >> - Implements memory hot(un)plug in Big Block Mode (BBM) >> >> I need one core-mm change, to make offline_and_remove_memory() eat bigger >> chunks. >> >> This series is based on "next-20201009" and can be found at: >> [email protected]:virtio-mem/linux.git virtio-mem-dbm-v1 >> > > I am trying to apply this patch set, while found I can't 'git fetch' this > repo. Is there any other repo I would apply this patch set? >
Sorry I tool the wrong repo. It‘s on my github: https://github.com/davidhildenbrand/linux/tree/virtio-mem-dbm-v1 > -- > Wei Yang > Help you, Help me >
_______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
