All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kinzler <ml-xen-devel@hfp.de>
To: Roderick Colenbrander <thunderbird2k@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Questions about GPLPV stability tests
Date: Wed, 30 Nov 2011 14:11:48 +0100	[thread overview]
Message-ID: <4ED62B94.4040502@hfp.de> (raw)
In-Reply-To: <CAEc3jaA3GgpGzP52D86qBMMRDNRBO7H08RDfxuF6pG609h96iA@mail.gmail.com>

>> The patch actually only disables HPET broadcast which has some downsides
>> because it effectively disables C3 states. Without C3 states Nehalem and
>> later CPUs cannot enter turbo-mode. So there is some loss of performance.
> Would disabling any low CPU power states and turbo clocks in the BIOS,
> help as well? Just curious. I have seen other 'weird' performance

I would leave the BIOS to its default and I'd guess that playing with 
BIOS settings only makes it worse.

> issues between machines using the same hardware. Some CPU intensive
> algorithm could be twice as slow running on Dom0 compared to the same
> kernel without Xen. On other identical systems I didn't see that
> issue. I didn't have time to investigate, but I felt there may have
> been BIOS setting differences.

Xen does not use the performance governor by default which has a notable 
performance impact in my tests. My Xen boot config is:

kernel /xen.gz dom0_mem=1024m dom0_max_vcpus=2 cpufreq=xen:performance
module /linux-2.6.32.36-pvops0-ak2 root=/dev/sda5

Regards Andreas

  reply	other threads:[~2011-11-30 13:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEc3jaBds7xmiKH8RMfmEHQumkEeZ3PopVfbZPs_B-Kz8-DsWw@mail.gmail.com>
2011-11-29 17:12 ` Questions about GPLPV stability tests Andreas Kinzler
2011-11-29 18:04   ` Roderick Colenbrander
2011-11-29 18:15     ` Andreas Kinzler
2011-11-29 18:21       ` Roderick Colenbrander
2011-11-30 13:11         ` Andreas Kinzler [this message]
2011-11-29 23:02       ` Konrad Rzeszutek Wilk
2011-11-30  0:01         ` Roderick Colenbrander
2011-12-06 19:12           ` Roderick Colenbrander
2011-12-07 20:38             ` Konrad Rzeszutek Wilk
2011-12-07 20:44               ` Roderick Colenbrander
2011-12-08 23:46                 ` Konrad Rzeszutek Wilk
2011-12-09  1:33                   ` Roderick Colenbrander
2011-12-09 22:02                     ` Roderick Colenbrander
2011-12-11 12:52                       ` Pasi Kärkkäinen
2011-12-11 18:58                         ` Roderick Colenbrander
2011-12-12 22:30                           ` Roderick Colenbrander
2011-12-13  1:50                             ` James Harper
2011-12-13  1:58                               ` Roderick Colenbrander
2011-12-13  2:02                             ` Konrad Rzeszutek Wilk
2011-12-13 21:20                               ` Konrad Rzeszutek Wilk
2011-12-16  2:25                                 ` Roderick Colenbrander
2011-12-26 18:45                                   ` Roderick Colenbrander
2012-01-03 16:55                                     ` Konrad Rzeszutek Wilk
2012-01-04 23:37                                       ` Roderick Colenbrander

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=4ED62B94.4040502@hfp.de \
    --to=ml-xen-devel@hfp.de \
    --cc=thunderbird2k@gmail.com \
    --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.