kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH] KVM: Don't update PPR on any APIC read
Date: Mon, 30 Jul 2012 20:48:09 -0300	[thread overview]
Message-ID: <20120730234809.GA31459@amt.cnet> (raw)
In-Reply-To: <1342968060-23683-1-git-send-email-avi@redhat.com>

On Sun, Jul 22, 2012 at 05:41:00PM +0300, Avi Kivity wrote:
> The current code will update the PPR on almost any APIC read; however
> that's only required if we read the PPR.
> 
> kvm_update_ppr() shows up in some profiles, albeit with a low usage (~1%).
> This should reduce it further (it will still be called during interrupt
> processing).
> 
> Signed-off-by: Avi Kivity <avi@redhat.com>

Applied, thanks.


      reply	other threads:[~2012-07-30 23:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-22 14:41 [PATCH] KVM: Don't update PPR on any APIC read Avi Kivity
2012-07-30 23:48 ` Marcelo Tosatti [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=20120730234809.GA31459@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    /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).