Jan Kiszka writes:
> On 2014-03-26 21:22, Bandan Das wrote:
>> Jan Kiszka writes:
>>
>>> On 2014-03-22 17:43, Bandan Das wrote:
Jan Kiszka writes:
> On 2014-03-20 21:58, Bandan Das wrote:
>> Jan Kiszka writes:
>>
>>> On 2014-03-20 04:28, Bandan Das wrote:
So
On 2014-03-26 21:22, Bandan Das wrote:
> Jan Kiszka writes:
>
>> On 2014-03-22 17:43, Bandan Das wrote:
>>> Jan Kiszka writes:
>>>
On 2014-03-20 21:58, Bandan Das wrote:
> Jan Kiszka writes:
>
>> On 2014-03-20 04:28, Bandan Das wrote:
>>> Some L1 hypervisors such as Xen see
Jan Kiszka writes:
> On 2014-03-22 17:43, Bandan Das wrote:
>> Jan Kiszka writes:
>>
>>> On 2014-03-20 21:58, Bandan Das wrote:
Jan Kiszka writes:
> On 2014-03-20 04:28, Bandan Das wrote:
>> Some L1 hypervisors such as Xen seem to be calling invept after
>> vmclear or bef
On 2014-03-22 17:43, Bandan Das wrote:
> Jan Kiszka writes:
>
>> On 2014-03-20 21:58, Bandan Das wrote:
>>> Jan Kiszka writes:
>>>
On 2014-03-20 04:28, Bandan Das wrote:
> Some L1 hypervisors such as Xen seem to be calling invept after
> vmclear or before vmptrld on L2. In this case
Jan Kiszka writes:
> On 2014-03-20 21:58, Bandan Das wrote:
>> Jan Kiszka writes:
>>
>>> On 2014-03-20 04:28, Bandan Das wrote:
Some L1 hypervisors such as Xen seem to be calling invept after
vmclear or before vmptrld on L2. In this case, proceed with
falling through and syncing
On 2014-03-20 21:58, Bandan Das wrote:
> Jan Kiszka writes:
>
>> On 2014-03-20 04:28, Bandan Das wrote:
>>> Some L1 hypervisors such as Xen seem to be calling invept after
>>> vmclear or before vmptrld on L2. In this case, proceed with
>>> falling through and syncing roots as a case where
>>> con
Paolo Bonzini writes:
> Il 20/03/2014 04:28, Bandan Das ha scritto:
>> Some L1 hypervisors such as Xen seem to be calling invept after
>> vmclear or before vmptrld on L2. In this case, proceed with
>> falling through and syncing roots as a case where
>> context wide invalidation can't be supporte
Jan Kiszka writes:
> On 2014-03-20 04:28, Bandan Das wrote:
>> Some L1 hypervisors such as Xen seem to be calling invept after
>> vmclear or before vmptrld on L2. In this case, proceed with
>> falling through and syncing roots as a case where
>> context wide invalidation can't be supported
>
> Ca
Il 20/03/2014 04:28, Bandan Das ha scritto:
Some L1 hypervisors such as Xen seem to be calling invept after
vmclear or before vmptrld on L2. In this case, proceed with
falling through and syncing roots as a case where
context wide invalidation can't be supported
Signed-off-by: Bandan Das
---
a
On 2014-03-20 04:28, Bandan Das wrote:
> Some L1 hypervisors such as Xen seem to be calling invept after
> vmclear or before vmptrld on L2. In this case, proceed with
> falling through and syncing roots as a case where
> context wide invalidation can't be supported
Can we also base this behaviour
Some L1 hypervisors such as Xen seem to be calling invept after
vmclear or before vmptrld on L2. In this case, proceed with
falling through and syncing roots as a case where
context wide invalidation can't be supported
Signed-off-by: Bandan Das
---
arch/x86/kvm/vmx.c | 5 +++--
1 file changed, 3
11 matches
Mail list logo