From: Dario Faggioli <dario.faggioli@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Wei Liu <wei.liu@citrix.com>, Jan Beulich <JBeulich@suse.com>
Subject: Re: some thoughts about merlot{0|1} issues [was: Re: [xen-unstable test] 102522: tolerable FAIL - PUSHED]
Date: Mon, 28 Nov 2016 17:45:02 +0100 [thread overview]
Message-ID: <1480351502.3178.13.camel@citrix.com> (raw)
In-Reply-To: <20161128151618.GF2304@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 1123 bytes --]
On Mon, 2016-11-28 at 10:16 -0500, Konrad Rzeszutek Wilk wrote:
> On Mon, Nov 28, 2016 at 08:48:30AM -0500, Boris Ostrovsky wrote:
> > IIRC some BIOSes indeed provided an option to disable C2. Dumping
> > SSDT
> > would tell us whether C2 is there is BIOS is not accessible.
>
> Dario, lastly - did you have xen-acpi-processor loaded or built in
> your kernel?
>
I'm sure it's there.
In fact, this is an OSSTest box in the colo. I've tried have a look
right now, without taking it off from OSSTest, but it does not have Xen
installed yet (I don't know what job it's executing).
Anyway, when the tests run, the kernel in use is the one build for all
the various tests and boxes of a flight, and it does has
XEN_ACPI_PROCESSOR. That's why I'm saying that I am sure it is there.
Anyway, I'll double check that.
Thanks 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
next prev parent reply other threads:[~2016-11-28 16:45 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 [this message]
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=1480351502.3178.13.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@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).