From: Luwei Kang <luwei.kang@intel.com>
To: xen-devel@lists.xen.org
Cc: andrew.cooper3@citrix.com, kevin.tian@intel.com,
Luwei Kang <luwei.kang@intel.com>,
jun.nakajima@intel.com, jbeulich@suse.com
Subject: [PATCH v2] X86/VPMU:clear the overflow status of which counter happened overflow
Date: Tue, 13 Dec 2016 10:49:36 +0800 [thread overview]
Message-ID: <1481597376-18175-1-git-send-email-luwei.kang@intel.com> (raw)
just set the corresponding bits of which counter happened overflow,
rather than set all the available bits of IA32_PERF_GLOBAL_OVF_CTRL
when happened pmu interrupt.
Signed-off-by: Luwei Kang <luwei.kang@intel.com>
---
v2:modify the description of this patch.
---
xen/arch/x86/cpu/vpmu_intel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/cpu/vpmu_intel.c b/xen/arch/x86/cpu/vpmu_intel.c
index e8049ed..613aafe 100644
--- a/xen/arch/x86/cpu/vpmu_intel.c
+++ b/xen/arch/x86/cpu/vpmu_intel.c
@@ -868,7 +868,7 @@ static int core2_vpmu_do_interrupt(struct cpu_user_regs *regs)
if ( is_pmc_quirk )
handle_pmc_quirk(msr_content);
core2_vpmu_cxt->global_status |= msr_content;
- msr_content = ~global_ovf_ctrl_mask;
+ msr_content &= ~global_ovf_ctrl_mask;
wrmsrl(MSR_CORE_PERF_GLOBAL_OVF_CTRL, msr_content);
}
else
--
2.7.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-12-13 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 2:49 Luwei Kang [this message]
2016-12-13 5:14 ` [PATCH v2] X86/VPMU:clear the overflow status of which counter happened overflow Tian, Kevin
2016-12-13 5:48 ` Kang, Luwei
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=1481597376-18175-1-git-send-email-luwei.kang@intel.com \
--to=luwei.kang@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xen.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).