All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Schiers <carsten@schiers.de>
To: "Tian, Kevin" <kevin.tian@intel.com>, "Yu, Ke" <ke.yu@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: AW: RE: RE: RE: RE: RE: No C-States any longer...
Date: Wed, 15 Jun 2011 11:12:09 +0200	[thread overview]
Message-ID: <10635020.231308129129960.JavaMail.root@uhura> (raw)

> this looks a bit strange. how about the native log?

I have not done a log with ACPI_DEBUG enabled. Will do so tonight or tomorrow night.

> what's your dom0 vcpu number? and how about physical cpu?

dom0_vcpu_pin/xend-config.sxp result in the following excerpt of xm vcpu-list:

  Name          ID          VCPU          CPU           State          ...
  Domain-0      0           0             0             r--            ...

  Domain-0      0           1             -             --p            ...

  Domain-0      0           2             -             --p            ...
  ...

> there's possibility that in your environment general ACPI code
> is changed which is not reflected in Xen specific versions. 

I have not understood that.

Thanks,
Carsten.

             reply	other threads:[~2011-06-15  9:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15  9:12 Carsten Schiers [this message]
2011-06-16  2:09 ` RE: RE: RE: RE: RE: No C-States any longer Tian, Kevin
  -- strict thread matches above, loose matches on Subject: below --
2011-06-16  6:22 AW: " Carsten Schiers
2011-06-15 13:06 Konrad Rzeszutek Wilk
2011-06-15 13:17 ` AW: " Carsten Schiers
2011-06-15  9:03 Carsten Schiers
2011-06-15  8:15 Tian, Kevin
2011-06-15  9:14 ` AW: " Carsten Schiers
2011-06-12  9:01 Tian, Kevin
2011-06-13 13:21 ` AW: " Carsten Schiers
2011-06-13 20:27   ` Carsten Schiers

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=10635020.231308129129960.JavaMail.root@uhura \
    --to=carsten@schiers.de \
    --cc=ke.yu@intel.com \
    --cc=kevin.tian@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.