On 16 September 2016 at 13:44, Alexander Graf <agraf@xxxxxxx> wrote: > >> On 16 Sep 2016, at 14:40, Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: >> >> >> >> On 16/09/2016 14:29, Christoffer Dall wrote: >>>> It may be useful for migrating a gicv2 VM to a gicv3 host without gicv2 emulation as well. >>> >>> I don't see why you'd do this; the VGIC hardware can perfectly well be >>> used for nesting as well, and this works rather well. >> >> Can GICv3 emulate GICv2 in a guest? > > It depends on the gicv3 configuration. As an SOC vendor you can either enable gicv2 compatibility or disable it. ThunderX for example is gicv3 only. LS2085 can handle gicv2 in the guest with gicv3 on the host. > Note that 'disabled' here means 'not implemented it in silicon', so there is no way you will ever be able to re-enable GICv2 compatibility on a ThunderX. Another thing to keep in mind is that GICv2 compatibility is disabled on the non-secure side if the secure side elects to configure its view of the GIC as v3 (i.e., in order to support >8 cores) -- 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
