From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Tim Deegan <Tim.Deegan@citrix.com>,
James Harper <james.harper@bendigoit.com.au>
Subject: Re: Poor HVM performance with 8 vcpus
Date: Wed, 07 Oct 2009 13:45:27 +0200 [thread overview]
Message-ID: <4ACC7F57.2040702@ts.fujitsu.com> (raw)
In-Reply-To: <de76405a0910070311q6c879be0wd4f33d8108235d8b@mail.gmail.com>
George Dunlap wrote:
> Jeurgen,
>
> I think this problem is a good candidate for xentrace/xenalyze. If
> you take a 30-second trace (xentrace -D -e all -T 30
> /tmp/[traceid].trace) while the benchmark is at its heaviest, and then
> analyze it using xenalyze
> (http://xenbits.xensource.com/ext/xenalyze.hg), it should show up
> whether the shadow performance is due to brute-force search or
> something else.
>
> If you're using 3.3, you'll have to apply the back-patch to xenalyze
> to make it work properly.
Patches don't apply cleanly, build fails with error even without patches due
to incorrect format strings.
Juergen
--
Juergen Gross Principal Developer Operating Systems
TSP ES&S SWE OS6 Telephone: +49 (0) 89 636 47950
Fujitsu Technolgy Solutions e-mail: juergen.gross@ts.fujitsu.com
Otto-Hahn-Ring 6 Internet: ts.fujitsu.com
D-81739 Muenchen Company details: ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2009-10-07 11:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 6:55 Poor HVM performance with 8 vcpus Juergen Gross
2009-10-07 7:26 ` Keir Fraser
2009-10-07 7:49 ` Juergen Gross
2009-10-07 7:56 ` Ian Pratt
2009-10-07 8:08 ` James Harper
2009-10-07 8:13 ` Ian Pratt
2009-10-07 8:31 ` Juergen Gross
2009-10-07 8:17 ` Keir Fraser
2009-10-07 9:12 ` Tim Deegan
2009-10-07 9:40 ` Juergen Gross
2009-10-07 10:11 ` George Dunlap
2009-10-07 11:45 ` Juergen Gross [this message]
2009-10-07 13:44 ` George Dunlap
[not found] ` <de76405a0910070627s7585c587l8753e40d1d2b77b9@mail.gmail.com>
[not found] ` <4ACC9C40.3030503@ts.fujitsu.com>
2009-10-07 14:24 ` George Dunlap
2009-10-08 5:00 ` Juergen Gross
2009-10-07 10:14 ` Tim Deegan
2009-10-07 12:32 ` Juergen Gross
2009-10-07 16:37 ` Gianluca Guida
2009-10-08 7:10 ` Juergen Gross
2009-10-14 8:16 ` Juergen Gross
2009-10-14 8:35 ` Keir Fraser
2009-10-14 9:11 ` Juergen Gross
2009-10-14 10:16 ` Gianluca Guida
2009-10-14 10:44 ` Juergen Gross
2009-10-14 10:49 ` Keir Fraser
2009-10-14 8:41 ` Tim Deegan
2009-10-14 9:17 ` Juergen Gross
2009-10-14 11:35 ` Gianluca Guida
2009-10-14 11:43 ` Juergen Gross
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=4ACC7F57.2040702@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=Tim.Deegan@citrix.com \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.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 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.