[PATCH 0/1] KVM: PPC: Increase memslots
Now that the patch from Nikunj to support the KVM_CAP_NR_MEMSLOTS capability on powerpc has been merged to kvm/next, we can/should increase the amount of memslots on ppc, too. Since nobody else sent a patch yet (as far as I can see), I'd like to suggest to increase the slot number to 320 now. Why 320? Well, x86 uses 509 (+3 internal slots), to give enough space for 256 pluggable DIMMs and 253 other slots (for PCI etc.). On powerpc, QEMU only supports 32 pluggable DIMMs, so I think we should be fine by using something around 253 + 32 slots + some few extra ... so 320 sounds like a good value to me for the time being (but in the long run, we should really make this dynamically instead, I think). Thomas Huth (1): KVM: PPC: Increase memslots to 320 arch/powerpc/include/asm/kvm_host.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 0/1] KVM: PPC: Increase memslots
Now that the patch from Nikunj to support the KVM_CAP_NR_MEMSLOTS capability on powerpc has been merged to kvm/next, we can/should increase the amount of memslots on ppc, too. Since nobody else sent a patch yet (as far as I can see), I'd like to suggest to increase the slot number to 320 now. Why 320? Well, x86 uses 509 (+3 internal slots), to give enough space for 256 pluggable DIMMs and 253 other slots (for PCI etc.). On powerpc, QEMU only supports 32 pluggable DIMMs, so I think we should be fine by using something around 253 + 32 slots + some few extra ... so 320 sounds like a good value to me for the time being (but in the long run, we should really make this dynamically instead, I think). Thomas Huth (1): KVM: PPC: Increase memslots to 320 arch/powerpc/include/asm/kvm_host.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
