lkml.org 
[lkml]   [2014]   [May]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: KVM Nested L2 guest startup problems
Il 07/05/2014 13:16, Abel Gordon ha scritto:
>> > PLE should be left enabled, I think.
> Well... the PLE settings L0 uses to run L1 (vmcs01) may be different
> than the PLE settings L1 configured to run L2 (vmcs12).
> For example, L0 can use a ple_gap to run L1 that is bigger than the
> ple_gap L1 configured to run L2. Or L0 can use a ple_window to run L1
> that is smaller than the ple_window L1 configured to run L2.

That's correct. We should leave PLE enabled while running L2, but hide
the feature altogether from L1.

Paolo

> So seems PLE should never be exposed to L1 or an appropriate nested
> handling needs to be implemented. Note the handling may become complex
> because in some cases a PLE exit from L2 should be handled directly by
> L0 and not passed to L1... remember nested preemption timer support :)
> ?



\
 
 \ /
  Last update: 2014-05-07 14:01    [W:0.077 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site