All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Cris Daniluk <cris.daniluk@gmail.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>,
	Jan Beulich <JBeulich@novell.com>
Subject: Re: Xen 4.0 crashes with pvops kernel
Date: Tue, 15 Jun 2010 11:11:07 -0400	[thread overview]
Message-ID: <20100615151107.GA4901@phenom.dumpdata.com> (raw)
In-Reply-To: <20100615141715.GF17817@reaktio.net>

On Tue, Jun 15, 2010 at 05:17:15PM +0300, Pasi Kärkkäinen wrote:
> On Tue, Jun 15, 2010 at 02:43:56PM +0100, Jan Beulich wrote:
> > >>> On 15.06.10 at 15:24, Cris Daniluk <cris.daniluk@gmail.com> wrote:
> > > For what its worth, it happened in 2.6.32.11 in addition to 2.6.32.13.
> > > I also had earlier tried a 2.6.31 pvops distro kernel with the same
> > > results last week. Interestingly, I also tried a 2.6.31 kernel with
> > > Xen 3.4 on the same hardware with no issues. It seems like XenLinux
> > > kernel with Xen 4.0 is fine, and pvops with Xen 3.x is fine.
> > 
> > That's odd, but perhaps the kernel behaves differently on older Xen.
> > Attempts to map IO-APIC space should be disallowed by 3.4 just as
> > with 4.0.
> >  
> 
> At least Xen 4.0 has the new IOAPIC hypercall that pvops 2.6.32 is using..

Yes and no. There are actually two ways of doing this: Using the
xen_acpi_register_gsi (or something akin to this) that makes a hypercall
to set the polarity/level of the IRQ. Then there is another which is to
map the IO APIC registers to dom0. The later is still present in 2.6.31
but not in 2.6.32.The upstream community did not like that mechanism of accessing
the IO APIC registers.

Soo, thanks to Jan's excellent knowledge of the ACPI spec and figuring
out that the DSDT tries to fiddle with the IO APIC registers we know
what the failure is.

Fixing it is another problem. Jan, any suggestions? Fixing the DSDT to
not do the store?

  reply	other threads:[~2010-06-15 15:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14 22:10 Xen 4.0 crashes with pvops kernel Cris Daniluk
2010-06-15  6:54 ` Jan Beulich
     [not found]   ` <AANLkTimslcbXQnihpIB0c-ceWbD7H-eyUY_BV2igyfzv@mail.gmail.com>
2010-06-15 12:50     ` Jan Beulich
2010-06-15 12:56       ` Keir Fraser
2010-06-15 13:20         ` Jan Beulich
2010-06-15 13:24           ` Cris Daniluk
2010-06-15 13:43             ` Jan Beulich
2010-06-15 13:49               ` Cris Daniluk
2010-06-15 14:13                 ` Jan Beulich
2010-06-15 14:35                   ` Cris Daniluk
2010-06-15 14:58                     ` Jan Beulich
2010-06-15 15:01                       ` Cris Daniluk
2010-06-15 15:21                         ` Jan Beulich
2010-06-15 16:18                           ` Boris Derzhavets
2010-06-15 14:17               ` Pasi Kärkkäinen
2010-06-15 15:11                 ` Konrad Rzeszutek Wilk [this message]
2010-06-16 14:42                   ` Jan Beulich
2010-06-15 13:57           ` Jan Beulich
2010-06-15 15:15             ` Konrad Rzeszutek Wilk
2010-06-16 14:36               ` Jan Beulich
2010-06-24  9:29             ` Jeremy Fitzhardinge
2010-06-24 11:30               ` Jan Beulich
2010-06-24 21:25                 ` Jeremy Fitzhardinge

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=20100615151107.GA4901@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@novell.com \
    --cc=cris.daniluk@gmail.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=pasik@iki.fi \
    --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.