public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Saso Slavicic <saso.linux@astim.si>, kvm@vger.kernel.org
Cc: lists2009@fnarfbargle.com, "'Nadav Amit'" <namit@cs.technion.ac.il>
Subject: Re: [PATCH stable] KVM: x86: Fix lost interrupt on irr_pending race
Date: Wed, 29 Apr 2015 18:45:37 +0200	[thread overview]
Message-ID: <55410AB1.4000300@redhat.com> (raw)
In-Reply-To: <000001d081cf$dd148fb0$973daf10$@astim.si>



On 28/04/2015 18:24, Saso Slavicic wrote:
> This will probably end up in RHEL6 sooner or later (but probably not before
> 6.7)?
> As I like to experiment a bit, would this patch do for -2.6.32-504.12.2.el6
> kernel? The code in that function is somewhat different...
> 
> --- a/arch/x86/kvm/lapic.c
> +++ b/arch/x86/kvm/lapic.c
> @@ -230,8 +230,13 @@
>  
>  static inline int apic_test_and_set_irr(int vec, struct kvm_lapic *apic)
>  {
> +	int ret = apic_test_and_set_vector(vec, apic->regs + APIC_IRR);
> +	/*
> +	 * irr_pending must be true if any interrupt is pending; set it
> after
> +	 * APIC_IRR to avoid race with apic_clear_irr
> +	 */
>  	apic->irr_pending = true;
> -	return apic_test_and_set_vector(vec, apic->regs + APIC_IRR);
> +	return ret;
>  }
>  
>  static inline int apic_search_irr(struct kvm_lapic *apic)
> 
> 
> Regards,

Yes, this exact same patch is brewing in the RHEL6.7 internal trees...

See https://bugzilla.redhat.com/show_bug.cgi?id=1213741

Paolo

      reply	other threads:[~2015-04-29 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1429602745-29882-1-git-send-email-pbonzini@redhat.com>
2015-04-21  8:47 ` [PATCH stable] KVM: x86: Fix lost interrupt on irr_pending race Paolo Bonzini
2015-04-22 13:34   ` Luis Henriques
2015-04-22 13:47     ` Paolo Bonzini
2015-04-22 13:52       ` Luis Henriques
2015-04-28 16:24   ` Saso Slavicic
2015-04-29 16:45     ` Paolo Bonzini [this message]

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=55410AB1.4000300@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lists2009@fnarfbargle.com \
    --cc=namit@cs.technion.ac.il \
    --cc=saso.linux@astim.si \
    /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