On Tue, 22 Jan 2019 12:44:18 +,
Heyi Guo wrote:
>
> Hi Marc,
>
> Thanks for your feedback. Please see my comments below.
>
>
> On 2019/1/22 17:53, Marc Zyngier wrote:
> > Hi Heyi,
> >
> > On Mon, 21 Jan 2019 11:51:48 +,
> > Heyi Guo wrote:
> >> Every VLPI will temporarily be mapped t
Hi Marc,
Thanks for your feedback. Please see my comments below.
On 2019/1/22 17:53, Marc Zyngier wrote:
Hi Heyi,
On Mon, 21 Jan 2019 11:51:48 +,
Heyi Guo wrote:
Every VLPI will temporarily be mapped to the first CPU in system
(normally CPU0) and then moved to the real scheduled CPU lat
Hi Heyi,
On Mon, 21 Jan 2019 11:51:48 +,
Heyi Guo wrote:
>
> Every VLPI will temporarily be mapped to the first CPU in system
> (normally CPU0) and then moved to the real scheduled CPU later. There
> is a time window so a VLPI may be sent to CPU0 instead of the real
> scheduled vCPU, in a mu
Every VLPI will temporarily be mapped to the first CPU in system
(normally CPU0) and then moved to the real scheduled CPU later. There
is a time window so a VLPI may be sent to CPU0 instead of the real
scheduled vCPU, in a multi-CPU virtual machine. However, CPU0 may have
not been scheduled as a vi
4 matches
Mail list logo