On 07/01/21 21:19, Sean Christopherson wrote:
That said, the v1 change had some appeal to it.
Which v1 change are you referring to?
Moving the to-be-injected event from eventinj to vcpu->arch, and from
there to vmcb02 on the next vmentry's inject_pending_event.
In the VMX case (if
On Thu, Jan 07, 2021, Paolo Bonzini wrote:
> On 07/01/21 10:38, Maxim Levitsky wrote:
> > The code to store it on the migration exists, but no code was restoring it.
> >
> > One of the side effects of fixing this is that L1->L2 injected events
> > are no longer lost when migration happens with
On 07/01/21 10:38, Maxim Levitsky wrote:
The code to store it on the migration exists, but no code was restoring it.
One of the side effects of fixing this is that L1->L2 injected events
are no longer lost when migration happens with nested run pending.
Signed-off-by: Maxim Levitsky
---
The code to store it on the migration exists, but no code was restoring it.
One of the side effects of fixing this is that L1->L2 injected events
are no longer lost when migration happens with nested run pending.
Signed-off-by: Maxim Levitsky
---
arch/x86/kvm/svm/nested.c | 4
1 file
4 matches
Mail list logo
