xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Joanna Rutkowska <joanna@invisiblethingslab.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Marek Marczykowski <marmarek@invisiblethingslab.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: Noticeably poor Intel GPU performance on 3.3 and 3.4 dom0 kernels
Date: Thu, 31 May 2012 11:15:03 +0200	[thread overview]
Message-ID: <4FC73697.20509@invisiblethingslab.com> (raw)
In-Reply-To: <4FC614770200007800086D0C@nat28.tlf.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1416 bytes --]

On 05/30/12 12:37, Jan Beulich wrote:
>>>> On 30.05.12 at 12:14, Joanna Rutkowska <joanna@invisiblethingslab.com> wrote:
>> > I've recently been some newer Dom0 kernels (3.3.5, 3.4) under Xen 4.1.2,
>> > and have noticed that those kernel noticeably downgrade performance of
>> > (at least) Intel GPUs. This is easily noticeable even on such trivial
>> > tasks as scrolling a webpage in Firefox or Chrome. This slow GPU
>> > performance on 3.3 and 3.4 kernels is in stark contrast with what I see
>> > on 3.2.7 Dom0 kernel, where graphics works just great...
>> > 
>> > In order to make sure that this is not caused by power management set
>> > too strictly, I played with xenpm and made sure to set the following:
>> > 1) xenpm set-scaling-governor performance
>> > 2) xenpm set-max-cstate 0
>> > 
>> > I have verified then that my processor: 1) keeps staying in P0 state
>> > (so, max frequency), and 2) keeps staying in C0 state.
>> > 
>> > Those setting didn't change anything regarding the poor graphics
>> > performance, though.
>> > 
>> > Any ideas what else I could test to find out the cause of this?
> To check whether the DRM drivers' supposedly more extensive
> use of the DMA API is the reason, could you check whether the
> performance is as bad with "mem=4G" on the Xen command line?

With mem=4G xen option, the graphics performance is just as poor as without.

joanna.


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

[-- Attachment #2: 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-05-31  9:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 10:14 Noticeably poor Intel GPU performance on 3.3 and 3.4 dom0 kernels Joanna Rutkowska
2012-05-30 10:37 ` Jan Beulich
2012-05-31  9:15   ` Joanna Rutkowska [this message]
2012-05-30 14:28 ` Konrad Rzeszutek Wilk
2012-05-30 14:57   ` Marek Marczykowski
2012-05-30 21:21     ` Konrad Rzeszutek Wilk

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=4FC73697.20509@invisiblethingslab.com \
    --to=joanna@invisiblethingslab.com \
    --cc=JBeulich@suse.com \
    --cc=marmarek@invisiblethingslab.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).