xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Jan Beulich <JBeulich@suse.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: Tue, 29 Nov 2016 12:06:06 +0100	[thread overview]
Message-ID: <1480417566.3178.29.camel@citrix.com> (raw)
In-Reply-To: <9cc151f4-c000-a358-5075-59a2064f074d@oracle.com>


[-- Attachment #1.1: Type: text/plain, Size: 1253 bytes --]

On Mon, 2016-11-28 at 13:27 -0500, Boris Ostrovsky wrote:
> On 11/28/2016 12:19 PM, Dario Faggioli wrote:
> > 
> > In any case, what I'm wondering is, could this ACPI / PM thing be
> > linked to the behavior we are seeing?
> 
> I find it somewhat unlikely.
> 
> BTW, I wouldn't worry about C2 specifically --- it's pretty clear
> that
> no C-state stats are collected at all:

[..]

> duration is the only reported value and most likely it's a NOW(). And
> the reason C1 is still mentioned is because it is a required C-state,
> whether or not it's in SSDT.
> 
I see.

> It is strange but I don't see anything in the serial log that would
> indicate a problem.
> 
Ok, thanks for looking. :-)

> > I'm not sure I see how... perhaps the system gets too hot and its
> > throttled down? (Yes, shooting in the dark, I know.)
> 
> I'd expect an event to be triggered (SMI?) and a warning of some sort
> to
> be printed.
> 
Indeed.

Thanks again and Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2016-11-29 11:06 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
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 [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=1480417566.3178.29.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.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).