[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8a0f0818-07eb-c33e-9488-5a69c6bb67b1@redhat.com>
Date: Thu, 16 Feb 2017 20:26:38 +0100
From: David Hildenbrand <david@...hat.com>
To: Paolo Bonzini <pbonzini@...hat.com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org
Cc: rkrcmar@...hat.com, christoffer.dall@...aro.org,
marc.zyngier@....com, james.hogan@...tec.com, paulus@...ba.org,
borntraeger@...ibm.com, cornelia.huck@...ibm.com,
kvmarm@...ts.cs.columbia.edu, kvm-ppc@...r.kernel.org
Subject: Re: [PATCH] KVM: race-free exit from KVM_RUN without POSIX signals
> post_kvm_run_save(vcpu);
> diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
> index 7964b970b9ad..f51d5082a377 100644
> --- a/include/uapi/linux/kvm.h
> +++ b/include/uapi/linux/kvm.h
> @@ -218,7 +218,8 @@ struct kvm_hyperv_exit {
> struct kvm_run {
> /* in */
> __u8 request_interrupt_window;
> - __u8 padding1[7];
> + __u8 immediate_exit;
As mentioned already on IRC, maybe something like "block_vcpu_run" would
fit better now.
But this is also ok and looks good to me.
Reviewed-by: David Hildenbrand <david@...hat.com>
--
Thanks,
David
Powered by blists - more mailing lists