RE: [RFC 0/6] KVM: arm/arm64: gsi routing support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 Hi!

> But personally I would prefer we
> check irqchip routing entries have flat mapping, ie gsi = irqchip.pin
> since in any case we don't want/expect the userspace to play with that.

 Why? On x86 userspace perfectly can play with it. We can imagine some very new qemu version in
future which has all arch-specific kludges like "direct mapping" removed and relying fully on
routing which it sets up from scratch, in the same way as x86 qemu does this. Or we can imagine some
new, legacy-free hypervisor implementation. The gsi == irqchip.pin limitation is just what we have
now by default, for backwards compatibility. But by design we were never obliged to stick to this.
 Well, it's just MHO...

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia


--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux