On 01/04/2012 03:10 AM, Alexander Graf wrote:
> From: Scott Wood <scottw...@freescale.com>
>
> Currently we check prior to returning from a lightweight exit,
> but not prior to initial entry.
>
> book3s already does a similar test.
>
> Signed-off-by: Scott Wood <scottw...@freescale.com>
> Signed-off-by: Alexander Graf <ag...@suse.de>
> ---
>  arch/powerpc/kvm/booke.c |   10 +++++++++-
>  1 files changed, 9 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/kvm/booke.c b/arch/powerpc/kvm/booke.c
> index b642200..9c78589 100644
> --- a/arch/powerpc/kvm/booke.c
> +++ b/arch/powerpc/kvm/booke.c
> @@ -322,11 +322,19 @@ int kvmppc_vcpu_run(struct kvm_run *kvm_run, struct 
> kvm_vcpu *vcpu)
>       }
>  
>       local_irq_disable();
> +
> +     if (signal_pending(current)) {
> +             kvm_run->exit_reason = KVM_EXIT_INTR;
> +             ret = -EINTR;
> +             goto out;
> +     }
> +
>       kvm_guest_enter();
>       ret = __kvmppc_vcpu_run(kvm_run, vcpu);
>       kvm_guest_exit();
> -     local_irq_enable();
>  
>

In general a single check prior to entry is sufficient (well, in
addition to the one in kvm_vcpu_block()).

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to