All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Kai <epimetreus@fastmail.fm>
Cc: Ray Lee <ray-lk@madrabbit.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Mike Galbraith <efault@gmx.de>
Subject: Re: Serious performance regression in Wine applications and Linux 2.6.24.*
Date: Thu, 27 Mar 2008 10:17:14 +0100	[thread overview]
Message-ID: <20080327091711.GD30918@elte.hu> (raw)
In-Reply-To: <1206341873.32060.1243929851@webmail.messagingengine.com>


* Kai <epimetreus@fastmail.fm> wrote:

> The issue only shows with Age of Wonders II and AoW Shadow Magic.
> 
> Every version of wine from 0.9.55 to 0.9.58, including several 
> intermediate git builds.
> 
> Xorg version 1.4.0.90, and a couple other versions (the problems has 
> persisted across a couple updates of Xorg)
> 
> Hardware rendering; using the prop. nV driver; updating that also 
> doesn't affect the issue, nor does retaining the same version.

could you run this script while such a slowdown is really prominent:

  http://people.redhat.com/mingo/cfs-scheduler/tools/cfs-debug-info.sh

and send me the output it generates? The output is the most useful if 
you do this on a kernel that has CONFIG_SCHED_DEBUG=y and 
CONFIG_SCHEDSTATS=y enabled.

on the off chance that this issue has been fixed in the soon-to-be 
2.6.25 kernel, you might also want to try x86.git/latest, which is based 
on the latest Linus tree and has all relevant x86 fixes and improvements 
added as well:

  http://people.redhat.com/mingo/x86.git/README

several of the changes can affect performance.

a third (and most comprehensive) way to debug this would be to send me a 
scheduler trace of such a slowdown, you can generate a scheduler trace 
the following way:

  http://people.redhat.com/mingo/sched-devel.git/readme-tracer.txt

but we can probably give a first estimation based on the cfs-debug-info 
output already. Btw., you can combine the scheduler and the x86 git tree 
into a temporary unified tree by doing these two commands:

  git-checkout -b tmp x86/latest
  git-merge sched-devel/latest

(run "make oldconfig" to pick up the new config options.)

	Ingo

  reply	other threads:[~2008-03-27  9:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23 22:10 Serious performance regression in Wine applications and Linux 2.6.24.* Kai
2008-03-23 22:22 ` Ray Lee
2008-03-24  6:57   ` Kai
2008-03-27  9:17     ` Ingo Molnar [this message]
2008-04-03 14:04       ` Kai
     [not found]       ` <1207250856.9779.1245934881@webmail.messagingengine.com>
2008-04-21 15:53         ` Ingo Molnar
2008-04-22  2:58           ` Kai
2008-08-07 15:05           ` Kai
2008-03-24  3:55 ` Andi Kleen
2008-03-24  6:54   ` Kai
2008-03-24  7:09     ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2008-03-23  2:49 Kai
2008-03-23  4:47 ` Ray Lee
2008-03-23 10:03   ` Kai
2008-03-25 12:12   ` Kai
2008-03-25 15:49     ` Ray Lee
     [not found]       ` <1207139425.16127.1245640599@webmail.messagingengine.com>
2008-04-02 12:40         ` Kai
2008-03-23 10:44 ` David
     [not found]   ` <1206309824.16550.1243881033@webmail.messagingengine.com>
2008-03-23 22:59     ` David

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=20080327091711.GD30918@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=efault@gmx.de \
    --cc=epimetreus@fastmail.fm \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray-lk@madrabbit.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.