On 2018/3/30 0:48, Marc Zyngier wrote:
> On Thu, 29 Mar 2018 16:27:58 +0100,
> Mark Rutland wrote:
>>
>> On Thu, Mar 29, 2018 at 11:00:24PM +0800, Shannon Zhao wrote:
>>> From: zhaoshenglong
>>>
>>> Currently the VMID for some VM is allocated during VCPU entry/exit
>>> context and will be update
On Thu, 29 Mar 2018 16:27:58 +0100,
Mark Rutland wrote:
>
> On Thu, Mar 29, 2018 at 11:00:24PM +0800, Shannon Zhao wrote:
> > From: zhaoshenglong
> >
> > Currently the VMID for some VM is allocated during VCPU entry/exit
> > context and will be updated when kvm_next_vmid inversion. So this will
On Thu, Mar 29, 2018 at 11:00:24PM +0800, Shannon Zhao wrote:
> From: zhaoshenglong
>
> Currently the VMID for some VM is allocated during VCPU entry/exit
> context and will be updated when kvm_next_vmid inversion. So this will
> cause the existing VMs exiting from guest and flush the tlb and ica
From: zhaoshenglong
Currently the VMID for some VM is allocated during VCPU entry/exit
context and will be updated when kvm_next_vmid inversion. So this will
cause the existing VMs exiting from guest and flush the tlb and icache.
Also, while a platform with 8 bit VMID supports 255 VMs, it can cr
