All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Peter Maloney <peter.maloney@brockmann-consult.de>
Cc: xen-devel@lists.xen.org
Subject: Re: 4.1.2 very slow without upstream patches, but fast with them, also 4.2 very slow
Date: Thu, 4 Oct 2012 10:25:38 -0400	[thread overview]
Message-ID: <20121004142538.GA9979@phenom.dumpdata.com> (raw)
In-Reply-To: <506C9A84.5040408@brockmann-consult.de>

On Wed, Oct 03, 2012 at 10:05:24PM +0200, Peter Maloney wrote:
> I also tested:
> modprobe xen-acpi-processor

You didn't say what kind of CPU you have. Nor if you compiled
your kernel or if you used a distros' kernel.

One thing (just to eliminate this being a power management issue),
is to do this on the Linux command line:

xen-acpi-processor.off=1

It would also help if you provided the .config you are using. There
are some options you should not have one (like XEN_DEBUGFS.. something).

  reply	other threads:[~2012-10-04 14:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 10:12 4.1.2 very slow without upstream patches, but fast with them, also 4.2 very slow Peter Maloney
2012-08-06 10:24 ` Andrew Cooper
2012-08-06 10:31 ` Jan Beulich
2012-08-07  7:25   ` Peter Maloney
2012-08-13 18:54     ` Peter Maloney
2012-08-13 20:59       ` Peter Maloney
2012-10-03 17:19         ` Peter Maloney
2012-10-03 20:05           ` Peter Maloney
2012-10-04 14:25             ` Konrad Rzeszutek Wilk [this message]
2012-10-05 20:19               ` Peter Maloney
2012-10-06  8:36                 ` Peter Maloney
2012-08-06 12:41 ` Malcolm Crossley
2012-08-06 14:02   ` Konrad Rzeszutek Wilk
     [not found]   ` <20120806140226.GB3093@phenom.dumpdata.com>
2012-08-07 21:42     ` M A Young
     [not found]     ` <alpine.DEB.2.00.1208072239120.8441@vega-c.dur.ac.uk>
2012-08-07 22:21       ` W. Michael Petullo

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=20121004142538.GA9979@phenom.dumpdata.com \
    --to=konrad@kernel.org \
    --cc=peter.maloney@brockmann-consult.de \
    --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.