On 22/02/18 16:02, Christoffer Dall wrote:
> On Thu, Feb 22, 2018 at 03:01:17PM +, Marc Zyngier wrote:
>> On Thu, 22 Feb 2018 14:42:27 +,
>> Christoffer Dall wrote:
>>>
>>> On Thu, Feb 22, 2018 at 12:32:11PM +, Marc Zyngier wrote:
On 15/02/18 21:03, Christoffer Dall wrote:
>
On Thu, Feb 22, 2018 at 03:01:17PM +, Marc Zyngier wrote:
> On Thu, 22 Feb 2018 14:42:27 +,
> Christoffer Dall wrote:
> >
> > On Thu, Feb 22, 2018 at 12:32:11PM +, Marc Zyngier wrote:
> > > On 15/02/18 21:03, Christoffer Dall wrote:
> > > > Just like we can program the GICv2
On Thu, 22 Feb 2018 14:42:27 +,
Christoffer Dall wrote:
>
> On Thu, Feb 22, 2018 at 12:32:11PM +, Marc Zyngier wrote:
> > On 15/02/18 21:03, Christoffer Dall wrote:
> > > Just like we can program the GICv2 hypervisor control interface directly
> > > from the core vgic code, we can do the
On Thu, Feb 22, 2018 at 12:32:11PM +, Marc Zyngier wrote:
> On 15/02/18 21:03, Christoffer Dall wrote:
> > Just like we can program the GICv2 hypervisor control interface directly
> > from the core vgic code, we can do the same for the GICv3 hypervisor
> > control interface on VHE systems.
> >
On 15/02/18 21:03, Christoffer Dall wrote:
> Just like we can program the GICv2 hypervisor control interface directly
> from the core vgic code, we can do the same for the GICv3 hypervisor
> control interface on VHE systems.
>
> We do this by simply calling the save/restore functions when we have
