From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com, bderzhavets@yahoo.com,
ke.yu@intel.com, carsten@schiers.de,
tom.goetz@virtualcomputer.com
Subject: Re: Re: [RFC PATCH] acpi/xen: Evaluate the _PDC properly (for 2.6.32, and 2.6.39)
Date: Wed, 15 Jun 2011 11:00:38 -0400 [thread overview]
Message-ID: <20110615150038.GD11705@dumpdata.com> (raw)
In-Reply-To: <4DF8DABF020000780004765C@nat28.tlf.novell.com>
On Wed, Jun 15, 2011 at 03:15:59PM +0100, Jan Beulich wrote:
> >>> On 15.06.11 at 15:46, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > I was trying to bring up an prototype box and it while it booted fine under
> > Linux, if I tried to do it under Dom0 with a modified Linux kernel it
> > crashed.
> > By modified I mean it had the "xen/acpi: add xen acpi processor driver"
> > patch in it.
> >
> > I traced it down to a one line fix which fixed the issue.
> > It might make sense to back-port this to the 2.6.32 tree, and it _might_ fix
>
> The parameter type change happened in 2.6.33.
Aha! That would explain why it was there - thank you for your sharp eye.
BTW, are there any good materials on explaining _PSS, _PDC, _P.. and C-states
and how to read the ACPI DSDT/SSDT to figure out what it has?
One of my AMD boxes on baremetal finds the _PSS tables but when
I boot under Xen it tells me it can't find it - and I am not even sure what they
look like in the ACPI tables.
next prev parent reply other threads:[~2011-06-15 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 13:46 [RFC PATCH] acpi/xen: Evaluate the _PDC properly (for 2.6.32, and 2.6.39) Konrad Rzeszutek Wilk
2011-06-15 14:15 ` Jan Beulich
2011-06-15 15:00 ` Konrad Rzeszutek Wilk [this message]
2011-06-15 15:18 ` Jan Beulich
2011-06-16 2:57 ` Tian, Kevin
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=20110615150038.GD11705@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@novell.com \
--cc=bderzhavets@yahoo.com \
--cc=carsten@schiers.de \
--cc=jeremy@goop.org \
--cc=ke.yu@intel.com \
--cc=tom.goetz@virtualcomputer.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.