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
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
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 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 Fri, 30 Mar 2018 09:56:10 +0800
Shannon Zhao wrote:
> 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
On 2018/3/30 17:01, Marc Zyngier wrote:
> On Fri, 30 Mar 2018 09:56:10 +0800
> Shannon Zhao wrote:
>
>> 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:
On Fri, 30 Mar 2018 17:52:07 +0800
Shannon Zhao wrote:
>
>
> On 2018/3/30 17:01, Marc Zyngier wrote:
> > On Fri, 30 Mar 2018 09:56:10 +0800
> > Shannon Zhao wrote:
> >
> >> On 2018/3/30 0:48, Marc Zyngier wrote:
> >>> On Thu, 29 Mar 2018 16:27:58 +0100,
> >>> Mark Rutland wrote:
>
> >>
On 2018/3/30 18:48, Marc Zyngier wrote:
> On Fri, 30 Mar 2018 17:52:07 +0800
> Shannon Zhao wrote:
>
>>
>>
>> On 2018/3/30 17:01, Marc Zyngier wrote:
>>> On Fri, 30 Mar 2018 09:56:10 +0800
>>> Shannon Zhao wrote:
>>>
On 2018/3/30 0:48, Marc Zyngier wrote:
> On Thu, 29 Mar 2018 16:27:5
On Fri, 30 Mar 2018 21:42:04 +0800
Shannon Zhao wrote:
> On 2018/3/30 18:48, Marc Zyngier wrote:
> > On Fri, 30 Mar 2018 17:52:07 +0800
> > Shannon Zhao wrote:
> >
> >>
> >>
> >> On 2018/3/30 17:01, Marc Zyngier wrote:
> >>> On Fri, 30 Mar 2018 09:56:10 +0800
> >>> Shannon Zhao wrote:
> >>
On Thu, Mar 29, 2018 at 04:27:58PM +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 wi
Hi Mark,
On 03/04/18 17:49, Mark Rutland wrote:
> On Thu, Mar 29, 2018 at 04:27:58PM +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
On 03/04/18 17:49, Mark Rutland wrote:
> On Thu, Mar 29, 2018 at 04:27:58PM +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
12 matches
Mail list logo