kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [PATCH] KVM: correctly detect APIC SW state in kvm_apic_post_state_restore()
Date: Thu, 09 Aug 2012 12:44:55 +0300	[thread overview]
Message-ID: <50238697.1030303@redhat.com> (raw)
In-Reply-To: <20120808122436.GF3341@redhat.com>

On 08/08/2012 03:24 PM, Gleb Natapov wrote:
> For apic_set_spiv() to track APIC SW state correctly it needs to see
> previous and next values of the spurious vector register, but currently
> memset() overwrite the old value before apic_set_spiv() get a chance to
> do tracking. Fix it by calling apic_set_spiv() before overwriting old
> value.
> 

Applied, thanks.


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

      reply	other threads:[~2012-08-09  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 12:24 [PATCH] KVM: correctly detect APIC SW state in kvm_apic_post_state_restore() Gleb Natapov
2012-08-09  9:44 ` Avi Kivity [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=50238697.1030303@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).