On 17 September 2016 at 16:38, Peter Maydell wrote:
> On 17 September 2016 at 16:28, Ard Biesheuvel
> wrote:
>> Another thing to keep in mind is that GICv2
>> compatibility is disabled on the non-secure side if the secure side
>> elects to
On 17 September 2016 at 16:28, Ard Biesheuvel wrote:
> 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)
If I'm
On 16 September 2016 at 13:44, Alexander Graf wrote:
>
>> On 16 Sep 2016, at 14:40, Paolo Bonzini 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
On Sat, 17 Sep 2016 11:58:48 +0530
Vijay Kilari wrote:
> On Fri, Sep 16, 2016 at 10:37 PM, Marc Zyngier wrote:
> > On 16/09/16 17:57, Vijay Kilari wrote:
> >> On Fri, Sep 16, 2016 at 8:06 PM, Marc Zyngier
> >> wrote:
>