On 24.09.19 16:45, Jan Beulich wrote:
On 24.09.2019 16:25, Jürgen Groß wrote:
On 23.09.19 17:24, Jan Beulich wrote:
On 14.09.2019 10:52, Juergen Gross wrote:
Today the vcpu runstate of a new scheduled vcpu is always set to
"running" even if at that time vcpu_runnable() is already returning
fal
On 24.09.2019 16:25, Jürgen Groß wrote:
> On 23.09.19 17:24, Jan Beulich wrote:
>> On 14.09.2019 10:52, Juergen Gross wrote:
>>> Today the vcpu runstate of a new scheduled vcpu is always set to
>>> "running" even if at that time vcpu_runnable() is already returning
>>> false due to a race (e.g. wit
On 23.09.19 17:24, Jan Beulich wrote:
On 14.09.2019 10:52, Juergen Gross wrote:
Today the vcpu runstate of a new scheduled vcpu is always set to
"running" even if at that time vcpu_runnable() is already returning
false due to a race (e.g. with pausing the vcpu).
I can see this part, ...
With
On 14.09.2019 10:52, Juergen Gross wrote:
> Today the vcpu runstate of a new scheduled vcpu is always set to
> "running" even if at that time vcpu_runnable() is already returning
> false due to a race (e.g. with pausing the vcpu).
I can see this part, ...
> With core scheduling this can no longer
Today the vcpu runstate of a new scheduled vcpu is always set to
"running" even if at that time vcpu_runnable() is already returning
false due to a race (e.g. with pausing the vcpu).
With core scheduling this can no longer work as not all vcpus of a
schedule unit have to be "running" when being sc
