ng Electronics Research center Russia
>
>
>> -Original Message-
>> From: Vijay Kilari [mailto:vijay.kil...@gmail.com]
>> Sent: Tuesday, August 11, 2015 6:16 PM
>> To: Pavel Fedin
>> Cc: kvmarm@lists.cs.columbia.edu; Christoffer Dall; Alex Bennée
>> Subject
Pavel Fedin
> Cc: kvmarm@lists.cs.columbia.edu; Christoffer Dall; Alex Bennée
> Subject: Re: KVM Live migration with GICv3
>
> On Tue, Aug 11, 2015 at 12:11 PM, Pavel Fedin wrote:
> > Hello!
> >
> >>I have prototyped Live migration with GICv3.
> >
>
On 11/08/15 06:25, Vijay Kilari wrote:
> Hi,
>
>I have prototyped Live migration with GICv3.
> For this I have made following changes
>
> 1) Save and Restore of GICv3 registers in QEMU.
> - For GICv2, QEMU is saving/restoring GICD, GICC registers. For GICv3,
> we have to save/restor
On 12 August 2015 at 17:17, Marc Zyngier wrote:
> If you plan to do anything for GICv3, you should only deal with with the
> system register version of the CPU interface.
Also, please make sure that you think about (and in terms of)
the underlying state inside the GIC, which is closely
related to
On 11/08/15 16:24, Pavel Fedin wrote:
> Hello!
>
>> I mean CPU interface registers GICC* defined for vgicv2 under
>> "vgic_cpu_ranges[]" in
>> virt/kvm/arm/vgic-v2-emul.c needs to be saved and restored for vgicv3 as
>> well.
>> So to access vgic_cpu_ranges[] for vgicv3, we need to register devi
Hello!
> I mean CPU interface registers GICC* defined for vgicv2 under
> "vgic_cpu_ranges[]" in
> virt/kvm/arm/vgic-v2-emul.c needs to be saved and restored for vgicv3 as well.
> So to access vgic_cpu_ranges[] for vgicv3, we need to register device
> for CPU registers space
> similar to gicv2 in
On Tue, Aug 11, 2015 at 12:11 PM, Pavel Fedin wrote:
> Hello!
>
>>I have prototyped Live migration with GICv3.
>
> This is interesting of course, i will need this for my project too and i was
> also going to take a look at this later.
>
>> For this I have made following changes
>>
>> 1) Sav
Hello!
>I have prototyped Live migration with GICv3.
This is interesting of course, i will need this for my project too and i was
also going to take a look at this later.
> For this I have made following changes
>
> 1) Save and Restore of GICv3 registers in QEMU.
> - For GICv2, QEMU
Hi,
I have prototyped Live migration with GICv3.
For this I have made following changes
1) Save and Restore of GICv3 registers in QEMU.
- For GICv2, QEMU is saving/restoring GICD, GICC registers. For GICv3,
we have to save/restore GICD, GICR and ICC registers.
However ICC regist
