Hollis Blanchard wrote:
> Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]>
>
Applied, thanks. Note that there is free advertising space between the
summary and the signoff that you can use to explain the change.
--
error compiling committee.c: too many arguments to function
--
Carsten Otte wrote:
> Avi Kivity wrote:
>
>> What about merging kvm_cpu_has_interrupt() into _runnable()?
>>
>> My feeling is that we can keep it separated.
>>
> On s390 there is a difference between has_interrupt and not runnable:
> CPUs can be in stopped state, and they can be in enabled
Avi Kivity wrote:
> What about merging kvm_cpu_has_interrupt() into _runnable()?
>
> My feeling is that we can keep it separated.
On s390 there is a difference between has_interrupt and not runnable:
CPUs can be in stopped state, and they can be in enabled wait (enabled
for interrupts, similar t
Carsten Otte wrote:
> Hollis Blanchard wrote:
>> Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]>
> Acked-by: Carsten Otte <[EMAIL PROTECTED]>
>
> We'll need this too on big iron.
What about merging kvm_cpu_has_interrupt() into _runnable()?
My feeling is that we can keep it separated.
--
err
Hollis Blanchard wrote:
> Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]>
Acked-by: Carsten Otte <[EMAIL PROTECTED]>
We'll need this too on big iron.
-
SF.Net email is sponsored by: The Future of Linux Business White Pape
Signed-off-by: Hollis Blanchard <[EMAIL PROTECTED]>
---
vcpu->mp_state looks like an arch-specific field, so what do we think about
this patch? It might make sense to fold the kvm_cpu_has_interrupt() test inside
kvm_arch_vcpu_runnable() as well.
2 files changed, 9 insertions(+), 3 deletions(-)
dri
