public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>, linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, Yoshida Nobuo <yoshida.nb@ncos.nec.co.jp>
Subject: Re: [PATCH 3/3] KVM: x86: make vapics_in_nmi_mode atomic
Date: Wed, 1 Jul 2015 15:33:41 +0200	[thread overview]
Message-ID: <5593EC35.6060509@redhat.com> (raw)
In-Reply-To: <1435695558-3168-4-git-send-email-rkrcmar@redhat.com>



On 30/06/2015 22:19, Radim Krčmář wrote:
> Writes were a bit racy, but hard to turn into a bug at the same time.
> (Particularly because modern Linux doesn't use this feature anymore.)

I suspect patch 2 makes this race much easier to trigger, so it deserves
Cc: stable@ as well.

Paolo

> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
> ---
>  arch/x86/include/asm/kvm_host.h | 2 +-
>  arch/x86/kvm/i8254.c            | 2 +-
>  arch/x86/kvm/lapic.c            | 4 ++--
>  3 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
> index c7fa57b529d2..2a7f5d782c33 100644
> --- a/arch/x86/include/asm/kvm_host.h
> +++ b/arch/x86/include/asm/kvm_host.h
> @@ -607,7 +607,7 @@ struct kvm_arch {
>  	struct kvm_pic *vpic;
>  	struct kvm_ioapic *vioapic;
>  	struct kvm_pit *vpit;
> -	int vapics_in_nmi_mode;
> +	atomic_t vapics_in_nmi_mode;
>  	struct mutex apic_map_lock;
>  	struct kvm_apic_map *apic_map;
>  
> diff --git a/arch/x86/kvm/i8254.c b/arch/x86/kvm/i8254.c
> index 4dce6f8b6129..f90952f64e79 100644
> --- a/arch/x86/kvm/i8254.c
> +++ b/arch/x86/kvm/i8254.c
> @@ -305,7 +305,7 @@ static void pit_do_work(struct kthread_work *work)
>  		 * LVT0 to NMI delivery. Other PIC interrupts are just sent to
>  		 * VCPU0, and only if its LVT0 is in EXTINT mode.
>  		 */
> -		if (kvm->arch.vapics_in_nmi_mode > 0)
> +		if (atomic_read(&kvm->arch.vapics_in_nmi_mode) > 0)
>  			kvm_for_each_vcpu(i, vcpu, kvm)
>  				kvm_apic_nmi_wd_deliver(vcpu);
>  	}
> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> index 8dc32b5a4e0d..954e98a8c2e3 100644
> --- a/arch/x86/kvm/lapic.c
> +++ b/arch/x86/kvm/lapic.c
> @@ -1264,9 +1264,9 @@ static void apic_manage_nmi_watchdog(struct kvm_lapic *apic, u32 lvt0_val)
>  		if (lvt0_in_nmi_mode) {
>  			apic_debug("Receive NMI setting on APIC_LVT0 "
>  				   "for cpu %d\n", apic->vcpu->vcpu_id);
> -			apic->vcpu->kvm->arch.vapics_in_nmi_mode++;
> +			atomic_inc(&apic->vcpu->kvm->arch.vapics_in_nmi_mode);
>  		} else
> -			apic->vcpu->kvm->arch.vapics_in_nmi_mode--;
> +			atomic_dec(&apic->vcpu->kvm->arch.vapics_in_nmi_mode);
>  	}
>  }
>  
> 

  reply	other threads:[~2015-07-01 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 20:19 [PATCH 0/3] KVM: x86: legacy NMI watchdog fixes Radim Krčmář
2015-06-30 20:19 ` [PATCH 1/3] KVM: x86: keep track of LVT0 changes under APICv Radim Krčmář
2015-06-30 20:19 ` [PATCH 2/3] KVM: x86: properly restore LVT0 Radim Krčmář
2015-07-01 13:29   ` Paolo Bonzini
2015-06-30 20:19 ` [PATCH 3/3] KVM: x86: make vapics_in_nmi_mode atomic Radim Krčmář
2015-07-01 13:33   ` Paolo Bonzini [this message]
2015-07-01 13:34 ` [PATCH 0/3] KVM: x86: legacy NMI watchdog fixes Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5593EC35.6060509@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkrcmar@redhat.com \
    --cc=yoshida.nb@ncos.nec.co.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox