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: Tue, 29 Nov 2011 19:15:57 +0100 [thread overview]
Message-ID: <4ED5215D.1010403@hfp.de> (raw)
In-Reply-To: <CAEc3jaAa7y8C2NNBn1=L3AhS0uuYFP6ze8o1cZ9yG2VYHx6qMA@mail.gmail.com>
>> Not in this year of my stability tests. In this year I am always
>> experiencing crashes of domU only. dom0 was always stable.
>> But last year, I hunted a very serious problem which causes nasty
>> hangs/crashes in dom0 (which crashes domU as a consequence). See this
>> mailing list post:
>> http://lists.xen.org/archives/html/xen-devel/2010-09/msg00556.html
>> In my tests it clearly shows that if you have a CPU without ARAT and you
>> don't have the patch from my post, your Xen 4.0.1 or 4.1.1 will crash under
>> load and/or after a while. What is your CPU?
> Most of our machines use i7 950 CPUs. They don't seem to have ARAT.
Yes, i7 950 does not have ARAT as it is the first Nehalem generation.
> Some other machines use Xeon CPUs with ARAT support. We never had
> issues on the Xeon systems, so we may actually be suffering from the
> ARAT issue. Are you still using the patch you linked to in a
> production environment?
Absolutely. As I mentioned I just re-performed tests recently and found
that even Xen 4.1.1 (earlier tests were for 4.0.1) is unstable without
my patch on non-ARAT-CPUs.
> I wonder why a cleaned up patch like that never made it into core.
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.
> I'm going to do some testing (may take a while).
Please let me know. There are already some people confirming that HPET
broadcast is buggy. With more evidence I will contact Keir again and
suggest to have it (HPET broadcast) fixed or removed.
Regards Andreas
next prev parent reply other threads:[~2011-11-29 18:15 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 [this message]
2011-11-29 18:21 ` Roderick Colenbrander
2011-11-30 13:11 ` Andreas Kinzler
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=4ED5215D.1010403@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 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).