On 08/14/2018 04:50 AM, Cornelia Huck wrote:
On Mon, 13 Aug 2018 17:48:02 -0400
Tony Krowiak wrote:
From: David Hildenbrand
VCPU requests and VCPU blocking right now don't take care of the vSIE
(as it was not necessary until now). But we want to have VCPU requests
that will also be handled
On 08/14/2018 04:50 AM, Cornelia Huck wrote:
On Mon, 13 Aug 2018 17:48:02 -0400
Tony Krowiak wrote:
From: David Hildenbrand
VCPU requests and VCPU blocking right now don't take care of the vSIE
(as it was not necessary until now). But we want to have VCPU requests
that will also be handled
On Mon, 13 Aug 2018 17:48:02 -0400
Tony Krowiak wrote:
> From: David Hildenbrand
>
> VCPU requests and VCPU blocking right now don't take care of the vSIE
> (as it was not necessary until now). But we want to have VCPU requests
> that will also be handled before running the vSIE again.
>
> So
On Mon, 13 Aug 2018 17:48:02 -0400
Tony Krowiak wrote:
> From: David Hildenbrand
>
> VCPU requests and VCPU blocking right now don't take care of the vSIE
> (as it was not necessary until now). But we want to have VCPU requests
> that will also be handled before running the vSIE again.
>
> So
From: David Hildenbrand
VCPU requests and VCPU blocking right now don't take care of the vSIE
(as it was not necessary until now). But we want to have VCPU requests
that will also be handled before running the vSIE again.
So let's simulate a SIE entry when entering the vSIE loop and check
for
From: David Hildenbrand
VCPU requests and VCPU blocking right now don't take care of the vSIE
(as it was not necessary until now). But we want to have VCPU requests
that will also be handled before running the vSIE again.
So let's simulate a SIE entry when entering the vSIE loop and check
for
6 matches
Mail list logo