From: George Dunlap <george.dunlap@eu.citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"JBeulich@suse.com" <JBeulich@suse.com>,
"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] Always save/restore performance counters when HVM guest switching VCPU
Date: Mon, 11 Mar 2013 11:11:02 +0000 [thread overview]
Message-ID: <513DBBC6.8030806@eu.citrix.com> (raw)
In-Reply-To: <69a6d98c-8200-48c6-adc7-fcc40347cffc@default>
On 08/03/13 15:11, Boris Ostrovsky wrote:
> ----- george.dunlap@eu.citrix.com wrote:
>
>> On 08/03/13 14:50, Boris Ostrovsky wrote:
>>> ----- JBeulich@suse.com wrote:
>>>
>>>>>>> On 04.03.13 at 13:42, George Dunlap
>> <George.Dunlap@eu.citrix.com>
>>>> wrote:
>>>>> On Fri, Mar 1, 2013 at 8:49 PM, <suravee.suthikulpanit@amd.com>
>>>> wrote:
>>>>>> From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
>>>>>>
>>>>>> Currently, the performance counter registers are saved/restores
>>>>>> when the HVM guest switchs VCPUs only if they are running.
>>>>>> However, PERF has one check where it writes the MSR and read
>> back
>>>>>> the value to check if the MSR is working. This has shown to
>> fails
>>>>>> the check if the VCPU is moved in between rdmsr and wrmsr and
>>>>>> resulting in the values are different.
>>>>> Many moons ago (circa 2005) when I used performance counters, I
>>>> found
>>>>> that adding them to the save/restore path added a non-neligible
>>>>> overhead -- something like 5% slow-down. Do you have any reason
>> to
>>>>> believe this is no longer the case? Have you done any benchmarks
>>>>> before and after?
>>> I was doing some VPMU tracing a couple of weeks ago and by looking
>> at
>>> trace timestamps I think I saw about 4000 cycles on VPMU save and
>>> ~9000 cycles on restore. Don't remember what it was percentage-wise
>> of
>>> a whole context switch.
>>>
>>> This was on Intel.
>> That's a really hefty expense to make all users pay on every context
>> switch, on behalf of a random check in a piece of software that only a
>> handful of people are going to be actually using.
> I believe Linux uses perf infrastructure to implement the watchdog.
Hmm -- well if it is the case that adding performance counters to the
vcpu context switch path will add a measurable overhead, then we
probably don't want them enabled for typical guests anyway. If people
are actually using the performance counters to measure performance, that
makes sense; but for watchdogs it seems like Xen should be able to
provide something that is useful for a watchdog without the extra
overhead of saving and restoring performance counters.
Konrad, any thoughts?
-George
next prev parent reply other threads:[~2013-03-11 11:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 15:11 [PATCH] Always save/restore performance counters when HVM guest switching VCPU Boris Ostrovsky
2013-03-11 11:11 ` George Dunlap [this message]
2013-03-11 14:53 ` Konrad Rzeszutek Wilk
2013-03-11 14:59 ` George Dunlap
2013-03-11 15:54 ` Boris Ostrovsky
2013-03-11 16:03 ` Jan Beulich
2013-03-12 8:18 ` Dietmar Hahn
2013-03-12 15:12 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2013-03-08 14:50 Boris Ostrovsky
2013-03-08 14:56 ` George Dunlap
2013-03-08 15:15 ` Jan Beulich
2013-03-01 20:49 suravee.suthikulpanit
2013-03-01 23:02 ` Boris Ostrovsky
2013-03-04 12:42 ` George Dunlap
2013-03-08 8:47 ` Jan Beulich
2013-03-08 22:52 ` Suravee Suthikulanit
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=513DBBC6.8030806@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=suravee.suthikulpanit@amd.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.