From: Gianluca Guida <gianluca.guida@eu.citrix.com>
To: George Dunlap <dunlapg@umich.edu>
Cc: Muli Ben-Yehuda <MULI@il.ibm.com>,
deshantm@gmail.com, Anthony Liguori <aliguori@us.ibm.com>,
xen-devel mailing list <xen-devel@lists.xensource.com>
Subject: Re: Re: Poor performance on HVM (kernbench)
Date: Thu, 11 Sep 2008 19:26:32 +0100 [thread overview]
Message-ID: <48C962D8.5030102@eu.citrix.com> (raw)
In-Reply-To: <de76405a0809111107r387487b5s7aa6d87d0401ce5@mail.gmail.com>
George Dunlap wrote:
> So, the problem appears to be with a ton of brute-force searches to
> remove writable mappings, both during resync and promotion. My
> analysis tool is reporting that of the 30 seconds or so in the trace
> from xen-unstable, the guest spent a whopping 67% in the hypervisor:
> * 26% doing resyncs as a result of marking another page out-of-sync
> * 9% promoting pages
> * 27% resyncing as a result of cr3 switches
> And almost the entirety of all of those can be attributed to
> brute-force searches to remove writable mappings.
Fantastic (well, sort of)!
If I understand it correctly, Todd is using PV drivers in Linux HVM
guests, so the reason for brute-force search is due to former L1
page-tables being used as I/O pages, not being unshadowed because they
can get writable mappings out of it.
It is, shortly, an unshadowing problem. Should be `easy` to fix. I
wasn't using PV drivers, so I was not experiencing this behaviour.
Or, it could be a fixup table bug, but I doubt it.
George, did you saw excessive fixup faults in the trace?
Todd, could you try without PV drivers (plain qemu emulation) and see if
the results get better?
Thanks,
Gianluca
next prev parent reply other threads:[~2008-09-11 18:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 18:23 Poor performance on HVM (kernbench) Todd Deshane
2008-09-10 21:22 ` Todd Deshane
2008-09-10 22:42 ` Anthony Liguori
2008-09-11 2:52 ` Todd Deshane
2008-09-11 9:35 ` George Dunlap
2008-09-11 15:30 ` Todd Deshane
2008-09-11 10:00 ` Gianluca Guida
2008-09-11 15:17 ` Gianluca Guida
2008-09-11 15:25 ` Gianluca Guida
2008-09-11 15:35 ` Todd Deshane
2008-09-11 16:48 ` Gianluca Guida
2008-09-11 17:25 ` Gianluca Guida
2008-09-11 18:07 ` George Dunlap
2008-09-11 18:26 ` Gianluca Guida [this message]
2008-09-11 19:04 ` Todd Deshane
2008-09-11 19:54 ` Todd Deshane
2008-09-11 20:02 ` Jeremy Fitzhardinge
2008-09-11 20:24 ` John Levon
2008-09-12 10:41 ` Gianluca Guida
2008-09-12 11:04 ` George Dunlap
2008-09-12 11:19 ` George Dunlap
2008-09-12 14:20 ` Jeremy Fitzhardinge
2008-09-10 21:37 ` Daniel Magenheimer
2008-09-10 21:42 ` Todd Deshane
2008-09-10 21:45 ` Daniel Magenheimer
2008-09-11 2:48 ` Todd Deshane
2008-09-10 21:51 ` Steve Ofsthun
2008-09-11 2:50 ` Todd Deshane
2008-09-11 6:31 ` Pasi Kärkkäinen
2008-09-11 16:02 ` Todd Deshane
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=48C962D8.5030102@eu.citrix.com \
--to=gianluca.guida@eu.citrix.com \
--cc=MULI@il.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=deshantm@gmail.com \
--cc=dunlapg@umich.edu \
--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.