This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: Poor performance on HVM (kernbench)

To: "Gianluca Guida" <gianluca.guida@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Poor performance on HVM (kernbench)
From: "George Dunlap" <dunlapg@xxxxxxxxx>
Date: Fri, 12 Sep 2008 12:04:38 +0100
Cc: Muli Ben-Yehuda <MULI@xxxxxxxxxx>, deshantm@xxxxxxxxx, Anthony Liguori <aliguori@xxxxxxxxxx>, xen-devel mailing list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 12 Sep 2008 04:05:10 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=DqKl3CBktKD2t67U1GavPOPPua3uxNspzzeMXxZROX0=; b=xufAifNnnV5pLd390jEx88DnPb8PTSAE8XCZRQkKm/jUmw5tILMBf/4VpBjniF7Pig WLBVLteUJj2N8Vjs0UlSQL2U/LZktKMRc/ODb0u2KyxPpBHd+6l2B7Rq7c6btpdZus52 ksejuxXwsGNz8Jj0ljZQK79LbLuR+klIofbUc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=sGQBh43pvWcqiFRNm7US2Cmyl3yVKnnzgGMSxMT7EO4D1p5Ty5rfrRoEu6ed8GfWI/ /RHIjVR/FG6KlNZcmRI+3YKZhkojoNE8Xl4AdRYbJjUddhEpg8yKRqgdobXXrfGt5e/s u6qOwImDXgID9EcOlD32WcA1Ucl0rdRejBYUw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48C962D8.5030102@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1e16a9ed0809101123m71a12030v7d06501f6467f93@xxxxxxxxxxxxxx> <1e16a9ed0809101422p6a58304dxaa1a92847109a518@xxxxxxxxxxxxxx> <48C8EC48.6080507@xxxxxxxxxxxxx> <48C9367B.6090003@xxxxxxxxxxxxx> <1e16a9ed0809110835p73165150t3f78d75b2f2ca8eb@xxxxxxxxxxxxxx> <48C9548C.4060709@xxxxxxxxxxxxx> <de76405a0809111107r387487b5s7aa6d87d0401ce5@xxxxxxxxxxxxxx> <48C962D8.5030102@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Sep 11, 2008 at 7:26 PM, Gianluca Guida
<gianluca.guida@xxxxxxxxxxxxx> wrote:
> Or, it could be a fixup table bug, but I doubt it.
> George, did you saw excessive fixup faults in the trace?

No, nothing excessive; 273,480 over 30 seconds isn't that bad.  The
main thing was that out of 15024 attempts to remove writable mappings,
13775 had to fall back to a brute-force search.

Looking at the trace, I can't really tell why there should be a
problem... I'm seeing tons of circumstances where there should only be
one writable mapping, but it falls back to brute-force search anyway.
Here's an example:

 24.999159660 -x  vmexit exit_reason EXCEPTION_NMI eip 2b105dcee330
 24.999159660 -x  wrmap-bf gfn 7453c
 24.999159660 -x fixup va 2b105f000000 gl1e 800000005caf0067 flags
 24.999748980 -x  vmentry
 24.999759577 -x  vmexit exit_reason EXCEPTION_NMI eip ffffffff8022a3b0
 24.999759577 -x fixup:unsync va ffff88007453c008 gl1e 7453c067 flags
 24.999762562 -x  vmentry
 25.002946338 -x  vmexit exit_reason CR_ACCESS eip ffffffff80491a63
 25.002946338 -x  wrmap-bf gfn 7e18c
 25.002946338 -x  oos resync full gfn 7e18c
 25.002946338 -x  wrmap-bf gfn 7453c
 25.002946338 -x  oos resync full gfn 7453c
 25.003526640 -x  vmentry

Here we see gfn 7453c:
 * promoted to be a shadow (the big 'P' in the flag string); at the
vmentry, there should be no writable mappings.
 * marked out-of-sync (one writable mapping, with fixup table)
 * re-sync'ed because of a CR write, and a brute-force search.

Note that the times behind the "wrmap-bf" and "oos resync full" are
not valid; but the whole vmexit->vmentry arc takes over 1.5


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>