From: Jian Zhou <jianjay.zhou@huawei.com>
To: Paolo Bonzini <pbonzini@redhat.com>, <herongguang.he@huawei.com>,
<zhang.zhanghailiang@huawei.com>, <gleb@kernel.org>,
<tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>,
<x86@kernel.org>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <weidong.huang@huawei.com>, <peter.huangpeng@huawei.com>
Subject: Re: [PATCH] KVM: VMX: enable LBR virtualization
Date: Thu, 15 Oct 2015 21:51:13 +0800 [thread overview]
Message-ID: <561FAF51.4090101@huawei.com> (raw)
In-Reply-To: <561E3CC8.7080309@redhat.com>
On 2015/10/14 19:30, Paolo Bonzini wrote:
>
>
> On 14/10/2015 13:26, Jian Zhou wrote:
>> On 12/10/2015 20:44, Paolo Bonzini wrote:
>>> In addition, the MSR numbers may differ between the guest and the host,
>>> because it is possible to emulate e.g. a Core CPU on a Core 2 CPU. So I
>>> recommend against using the atomic switch mechanism for the from/to MSRs.
>>
>> The vLBR feature depends on vPMU, and to enable vPMU, it needs to
>> specify the "cpu mode" in the guest XML as host-passthrough. I think
>> the MSR numbers between the guest and the host are the same in this
>> senario.
>
> Does it depend on vPMU _for Linux guests_ or in general? My impression
> is that LBR can be used by the guest independent of the PMU.
I think only for Linux guests.
I googled how to enable LBR on other guests(except Linux guests),
e.g. Windows, and got no developer manuals about it.
Here is an article about it:
http://www.codeproject.com/Articles/517466/Last-branch-records-
and-branch-tracing
it says:
"bit 8 of DR7 represents bit 0 of DebugCtl. This is the LBR bit."
Intel developer manual vol 3B introduced DR7(Debug Control Register)
and bit 8 of it on Section 17.2.4:
"LE and GE (local and global exact breakpoint enable) flags (bits 8,
9) — When set, these flags cause the processor to detect the exact
instruction that caused a data breakpoint condition. For backward and
forward compatibility with other Intel processors, we recommend that
the LE and GE flags be set to 1 if exact breakpoints are required."
But for now, I don't know how to test bit 8 of DR7 on Windows.
Regards,
Jian
>
>
>
next prev parent reply other threads:[~2015-10-15 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1444471906-8496-1-git-send-email-jianjay.zhou@huawei.com>
2015-10-12 12:10 ` [PATCH] KVM: VMX: enable LBR virtualization Jian Zhou
2015-10-12 12:44 ` Paolo Bonzini
2015-10-14 11:26 ` Jian Zhou
2015-10-14 11:30 ` Paolo Bonzini
2015-10-15 13:51 ` Jian Zhou [this message]
2015-10-15 15:03 ` Paolo Bonzini
2015-10-16 0:54 ` Jian Zhou
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=561FAF51.4090101@huawei.com \
--to=jianjay.zhou@huawei.com \
--cc=gleb@kernel.org \
--cc=herongguang.he@huawei.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=tglx@linutronix.de \
--cc=weidong.huang@huawei.com \
--cc=x86@kernel.org \
--cc=zhang.zhanghailiang@huawei.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).