From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v2] KVM: VMX: Conditionally reload debug register 6
Date: Wed, 2 Sep 2009 15:54:53 -0300 [thread overview]
Message-ID: <20090902185453.GA4238@amt.cnet> (raw)
In-Reply-To: <1251810385-21050-1-git-send-email-avi@redhat.com>
On Tue, Sep 01, 2009 at 04:06:25PM +0300, Avi Kivity wrote:
> Only reload debug register 6 if we're running with the guest's
> debug registers. Saves around 150 cycles from the guest lightweight
> exit path.
>
> dr6 contains a couple of bits that are updated on #DB, so intercept
> that unconditionally and update those bits then.
Applied, thanks.
next prev parent reply other threads:[~2009-09-02 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 13:06 [PATCH v2] KVM: VMX: Conditionally reload debug register 6 Avi Kivity
2009-09-01 13:15 ` Jan Kiszka
2009-09-01 13:35 ` Avi Kivity
2009-09-01 13:47 ` Jan Kiszka
2009-09-01 16:21 ` Avi Kivity
2009-09-02 18:54 ` Marcelo Tosatti [this message]
2009-09-03 8:20 ` Jan Kiszka
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=20090902185453.GA4238@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.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).