On 29/03/16 14:12, Vladimir Murzin wrote: > Hi Andre, > > On 25/03/16 02:04, Andre Przywara wrote: >> Please have a look at the series, review it and give the code some >> serious testing (and possibly debugging). All feedback is appreciated. > > I see that with the new vgic implementation kvmtool starts throwing: > > kvm [1273]: Unable to register VGICv3 redist MMIO regions > It comes from kvm_io_bus_register_dev() if (bus->dev_count - bus->ioeventfd_count > NR_IOBUS_DEVS - 1) return -ENOSPC; with bus->dev_count being 1000 [<ffffffc00009f93c>] kvm_io_bus_register_dev+0x130/0x148 [<ffffffc0000ad274>] kvm_vgic_register_mmio_region+0xac/0xdc [<ffffffc0000ad4d4>] vgic_register_redist_regions+0xb8/0x158 [<ffffffc0000abb90>] vgic_v3_map_resources+0x5c/0xf0 [<ffffffc0000aae04>] kvm_vgic_map_resources+0x40/0x84 [<ffffffc0000a23d0>] kvm_arch_vcpu_ioctl_run+0x3f0/0x400 [<ffffffc00009d484>] kvm_vcpu_ioctl+0x2d4/0x6ec [<ffffffc0001c4eec>] do_vfs_ioctl+0xb4/0x760 [<ffffffc0001c561c>] SyS_ioctl+0x84/0x98 [<ffffffc000085d30>] el0_svc_naked+0x24/0x28 Hope this helps... Vladimir > for --cpus 58 and above, where with the old vgic it is quite happy with > up to 255 cpus. > > Cheers > Vladimir > _______________________________________________ > kvmarm mailing list > kvmarm@xxxxxxxxxxxxxxxxxxxxx > https://lists.cs.columbia.edu/mailman/listinfo/kvmarm > > _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
