On 08/11/17 08:44, Auger Eric wrote: > Hi Marc, > > On 27/10/2017 16:28, Marc Zyngier wrote: >> All it takes is the has_v4 flag to be set in gic_kvm_info >> as well as "kvm-arm.vgic_v4_enable=1" being passed on the >> command line for GICv4 to be enabled in KVM. > > What did you motivate your choice of having an enable option instead of > a disable option? Currently, SW MSI injection works really well. It's been validated, plenty of people are using it. On the other hand, GICv4 is new and probably buggy. I only know of 2 other people having tried it. I'm also not sure it gives the best possible performance in the general use case (oversubscribed host with freely migrating vcpus). Given that, I'm not keen on making it the default. But if you can report that it is better and more reliable than SW injection, I'll switch the default the other way around! ;-) Thanks, M. -- Jazz is not dead. It just smells funny... _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
