All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maloney <peter.maloney@brockmann-consult.de>
To: xen-devel@lists.xen.org, Andres Lagar-Cavilla <andres@lagarcavilla.org>
Subject: Re: xen-unstable, winxp32 very poor performance on AMD FX-8150, I bisected and changeset is 24770:7f79475d3de7
Date: Thu, 22 Nov 2012 19:54:18 +0100	[thread overview]
Message-ID: <50AE74DA.6080808@brockmann-consult.de> (raw)
In-Reply-To: <50A2484D.309@brockmann-consult.de>

[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]

On 11/13/2012 02:17 PM, Peter Maloney wrote:
> On 2012-11-01 18:28, Andres Lagar-Cavilla wrote:
>> On Nov 1, 2012, at 1:00 PM, Tim Deegan <tim@xen.org> wrote:
>>
>>> Hi,
>>>
>>> At 14:59 +0100 on 22 Oct (1350917960), Tim Deegan wrote:
>>>> At 19:21 +0200 on 20 Oct (1350760876), Peter Maloney wrote:
>>>>> The change was 8 months ago
>>>>>
>>>>> changeset:   24770:7f79475d3de7
>>>>> user:        Andres Lagar-Cavilla <andres@lagarcavilla.org>
>>>>> date:        Fri Feb 10 16:07:07 2012 +0000
>>>>> summary:     x86/mm: Make p2m lookups fully synchronized wrt modifications
>>> [...]
>> Not any immediate ideas without profiling.
>>
>> However, most callers of hvmemul_do_io pass a stub zero ram_gpa address. We might be madly hitting the p2m locks for no reason there.
>>
>> How about the following patch, Peter, Tim?
>

I tried the patch applied to xen-unstable 4.2.0-branched
528f0708b6db+ 4.2.0-branched

It seemed the same. It was extremely slow with 7 vcpus, and with 2 vcpus
it was slow, but fast enough that I could bother to log in and out
during the test.

Attached are logs generated with this command (using xm instead of xl):
for i in {1..30}; do xm debug-keys d; xm dmesg -c; done >> nameoflog

xenxp_xm_dmesg_-c_7cpus_idle.log
xenxp_xm_dmesg_-c_7cpus_logintooslow.log
xenxp_xm_dmesg_-c_7cpus_shutdown.log
xenxp_xm_dmesg_-c_duringlogin.log
xenxp_xm_dmesg_-c_idling_login_screen.log

Also there is xenxp_dmesg.log which is output from hitting alt+sysrq+w
and p in case it's relevant.

BTW this time I am testing with kernel 3.6.7

[-- Attachment #2: xenxp_logs.tgz --]
[-- Type: application/x-compressed-tar, Size: 328293 bytes --]

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-11-22 18:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20 17:21 xen-unstable, winxp32 very poor performance on AMD FX-8150, I bisected and changeset is 24770:7f79475d3de7 Peter Maloney
2012-10-20 18:40 ` Peter Maloney
2012-10-22 13:56 ` Andres Lagar-Cavilla
2012-10-22 13:59 ` Tim Deegan
2012-10-23 22:17   ` Peter Maloney
2012-11-01 17:00   ` Tim Deegan
2012-11-01 17:28     ` Andres Lagar-Cavilla
2012-11-13 13:17       ` Peter Maloney
2012-11-22 18:54         ` Peter Maloney [this message]
2013-01-12 15:25           ` Peter Maloney
2013-01-17 20:57             ` Pasi Kärkkäinen
2013-01-18 14:22               ` George Dunlap
2013-01-18 14:40                 ` Andres Lagar-Cavilla
2013-01-21 12:07                   ` George Dunlap
2013-01-18 14:30             ` George Dunlap
2013-01-26 12:30               ` Peter Maloney

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=50AE74DA.6080808@brockmann-consult.de \
    --to=peter.maloney@brockmann-consult.de \
    --cc=andres@lagarcavilla.org \
    --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.