From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Dario Faggioli <dario.faggioli@citrix.com>,
osstest-admin@xenproject.org
Subject: Re: [xen-unstable test] 88047: regressions - FAIL
Date: Fri, 01 Apr 2016 09:32:34 -0600 [thread overview]
Message-ID: <56FEB0B202000078000E2397@prv-mh.provo.novell.com> (raw)
In-Reply-To: <22270.35855.258398.817550@mariner.uk.xensource.com>
>>> On 01.04.16 at 16:56, <Ian.Jackson@eu.citrix.com> wrote:
> Dario Faggioli writes ("Re: [Xen-devel] [xen-unstable test] 88047: regressions -
> FAIL"):
>> On Fri, 2016-04-01 at 07:44 -0600, Jan Beulich wrote:
>> > Might it be worth trying whether that's a deep C-state issue (by
>> > temporarily limiting their use of deep C states)?
>
> I'm happy to try this.
>
>> IIRC, it's the box(es) with the weird NUMA setup... something about
>> nodes without any memory:
>
> Right.
>
>> Not that I see how this could cause the long latencies / timeouts, though...
> :-/
>>
>> In any case, I think Jan's C states suggestion is worth a shot.
>
> Forgive my ignorance, but how would I do that ?
As a first shot, disable them altogether by "max_cstate=1" on the
hypervisor command line. If that helps, we can bi-sect deeper
states as well as see whether there's a difference between the two
idle drivers.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-01 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 6:12 [xen-unstable test] 88047: regressions - FAIL osstest service owner
2016-04-01 9:43 ` Jan Beulich
2016-04-01 13:36 ` Ian Jackson
2016-04-01 13:44 ` Jan Beulich
2016-04-01 14:40 ` Dario Faggioli
2016-04-01 14:56 ` Ian Jackson
2016-04-01 15:32 ` Jan Beulich [this message]
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=56FEB0B202000078000E2397@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xenproject.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).