On Thu, May 24, 2018 at 10:18:39AM +0100, Alex Bennée wrote:
>
> Christoffer Dall writes:
>
> > On Wed, May 23, 2018 at 03:40:26PM +0100, Dave Martin wrote:
> >> On Wed, May 23, 2018 at 03:34:20PM +0100, Alex Bennée wrote:
> >> >
> >> > Dave Martin writes:
[...]
> >> > > diff --git a/virt/kvm
Christoffer Dall writes:
> On Wed, May 23, 2018 at 03:40:26PM +0100, Dave Martin wrote:
>> On Wed, May 23, 2018 at 03:34:20PM +0100, Alex Bennée wrote:
>> >
>> > Dave Martin writes:
>> >
>> > > From: Christoffer Dall
>> > >
>> > > KVM/ARM differs from other architectures in having to maintain
On Wed, May 23, 2018 at 03:40:26PM +0100, Dave Martin wrote:
> On Wed, May 23, 2018 at 03:34:20PM +0100, Alex Bennée wrote:
> >
> > Dave Martin writes:
> >
> > > From: Christoffer Dall
> > >
> > > KVM/ARM differs from other architectures in having to maintain an
> > > additional virtual address
On Wed, May 23, 2018 at 03:34:20PM +0100, Alex Bennée wrote:
>
> Dave Martin writes:
>
> > From: Christoffer Dall
> >
> > KVM/ARM differs from other architectures in having to maintain an
> > additional virtual address space from that of the host and the
> > guest, because we split the executio
Dave Martin writes:
> From: Christoffer Dall
>
> KVM/ARM differs from other architectures in having to maintain an
> additional virtual address space from that of the host and the
> guest, because we split the execution of KVM across both EL1 and
> EL2.
>
> This results in a need to explicitly
From: Christoffer Dall
KVM/ARM differs from other architectures in having to maintain an
additional virtual address space from that of the host and the
guest, because we split the execution of KVM across both EL1 and
EL2.
This results in a need to explicitly map data structures into EL2
(hyp) wh
