From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>,
Dario Faggioli <dario.faggioli@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Wei Liu <wei.liu@citrix.com>
Subject: Re: some thoughts about merlot{0|1} issues [was: Re: [xen-unstable test] 102522: tolerable FAIL - PUSHED]
Date: Mon, 28 Nov 2016 08:48:30 -0500 [thread overview]
Message-ID: <9d03797a-0c29-e703-ffd2-fdba184f60a1@oracle.com> (raw)
In-Reply-To: <583715CF0200007800121D4D@prv-mh.provo.novell.com>
On 11/24/2016 10:31 AM, Jan Beulich wrote:
>>>> On 24.11.16 at 16:14, <dario.faggioli@citrix.com> wrote:
>> When dumping ACPI C states, here's how things look like for _all_ CPUs:
>> Nov 23 13:13:00.382134 (XEN) ==cpu3==
>> Nov 23 13:13:00.382157 (XEN) active state: C-1
>> Nov 23 13:13:00.390096 (XEN) max_cstate: C7
>> Nov 23 13:13:00.390125 (XEN) states:
>> Nov 23 13:13:00.390148 (XEN) C1: type[C1] latency[000] usage[00000000] method[ HALT] duration[0]
>> Nov 23 13:13:00.398055 (XEN) C0: usage[00000000] duration[4229118701384]
>> Nov 23 13:13:00.398090 (XEN) PC2[0] PC3[0] PC6[0] PC7[0]
>> Nov 23 13:13:00.406088 (XEN) CC3[0] CC6[0] CC7[0]
>>
>> And I checked other runs, and it's the same everywhere.
>>
>> I remember that Jan suggested trying to pass max_cstate=1 to Xen at
>> boot. I was about to ask Ian to do that for this host, but it looks
>> like we're using only C0 and C1 already anyway.
> This indeed looks surprising for a half way modern system - is the
> BIOS perhaps limiting C-states (maybe instructed to via BIOS setup)?
IIRC some BIOSes indeed provided an option to disable C2. Dumping SSDT
would tell us whether C2 is there is BIOS is not accessible.
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-28 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 15:54 [xen-unstable test] 102522: tolerable FAIL - PUSHED osstest service owner
2016-11-24 15:14 ` some thoughts about merlot{0|1} issues [was: Re: [xen-unstable test] 102522: tolerable FAIL - PUSHED] Dario Faggioli
2016-11-24 15:31 ` Jan Beulich
2016-11-28 13:48 ` Boris Ostrovsky [this message]
2016-11-28 15:16 ` Konrad Rzeszutek Wilk
2016-11-28 16:08 ` Andrew Cooper
2016-11-28 16:20 ` Jan Beulich
2016-11-28 16:45 ` Dario Faggioli
2016-11-28 17:06 ` Dario Faggioli
2016-11-28 17:19 ` Dario Faggioli
2016-11-28 18:27 ` Boris Ostrovsky
2016-11-29 11:06 ` Dario Faggioli
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=9d03797a-0c29-e703-ffd2-fdba184f60a1@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=dario.faggioli@citrix.com \
--cc=wei.liu@citrix.com \
--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).