From: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>
To: xen-devel@lists.xen.org
Cc: Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 2 of 2] V2 vpmu: Add the BTS extension
Date: Fri, 16 Mar 2012 09:58:06 +0100 [thread overview]
Message-ID: <2331989.zfZYpXceWs@amur> (raw)
In-Reply-To: <4F6207770200007800078B07@nat28.tlf.novell.com>
Am Donnerstag 15 März 2012, 14:15:03 schrieb Jan Beulich:
>
> Committed both patches, but please take a look since - as indicated - I
> made a few adjustments.
Thanks for the adjustments Jan, works very well!
Only a small fix for console logging beauty ;-) :
diff -r 1b68427875f7 xen/arch/x86/hvm/vmx/vpmu_core2.c
--- a/xen/arch/x86/hvm/vmx/vpmu_core2.c Thu Mar 15 15:20:37 2012 +0000
+++ b/xen/arch/x86/hvm/vmx/vpmu_core2.c Fri Mar 16 09:40:16 2012 +0100
@@ -690,7 +690,7 @@ static int core2_vpmu_initialise(struct
printk("******************************************************\n");
printk("** WARNING: Emulation of BTS Feature is switched on **\n");
printk("** Using this processor feature in a virtualized **\n");
- printk("** environment is not 100%% safe. **\n");
+ printk("** environment is not 100%% safe. **\n");
printk("** Setting the DS buffer address with wrong values **\n");
printk("** may lead to hypervisor hangs or crashes. **\n");
printk("** It is NOT recommended for production use! **\n");
Dietmar.
> Jan
>
--
Company details: http://ts.fujitsu.com/imprint.html
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-03-16 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 13:13 [PATCH 2 of 2] V2 vpmu: Add the BTS extension Dietmar Hahn
2012-03-13 14:22 ` Jan Beulich
2012-03-15 13:39 ` Dietmar Hahn
2012-03-15 14:15 ` Jan Beulich
2012-03-16 8:58 ` Dietmar Hahn [this message]
2012-03-16 9:16 ` Jan Beulich
2012-03-16 10:25 ` Dietmar Hahn
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=2331989.zfZYpXceWs@amur \
--to=dietmar.hahn@ts.fujitsu.com \
--cc=JBeulich@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.