From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Todd Deshane <deshantm@gmail.com>,
Andrew Lyon <andrew.lyon@gmail.com>,
xen-devel@lists.xensource.com
Subject: Re: pv_ops dom0 kernel failure with ata_piix / irq problems
Date: Fri, 30 Jan 2009 10:50:51 -0800 [thread overview]
Message-ID: <49834C0B.1030309@goop.org> (raw)
In-Reply-To: <1233339380.9970.45.camel@zakaz.uk.xensource.com>
Ian Campbell wrote:
> On Fri, 2009-01-30 at 18:12 +0000, Ian Campbell wrote:
>
>> Possibly the correct fix might be to use xen_register_gsi() here
>> instead of xen_allocate_pirq() and get rid of the special case for IRQ
>> 14 and 15 in xen_pci_pirq_enable(). Maybe only 14 and 15 need this
>> special treatment.
>>
>
> FWIW this also Works For Me.
>
OK. I'd noticed that the native code just sets up all the legacy
interrupts at once. I guess we should follow the lead to avoid these
kinds of init order problems.
J
next prev parent reply other threads:[~2009-01-30 18:50 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 14:34 pv_ops dom0 kernel crashes Pasi Kärkkäinen
2008-12-30 14:44 ` Pasi Kärkkäinen
2008-12-30 16:03 ` Todd Deshane
2008-12-30 16:19 ` Pasi Kärkkäinen
2008-12-30 16:28 ` Pasi Kärkkäinen
2008-12-30 16:47 ` Todd Deshane
2008-12-30 16:52 ` Pasi Kärkkäinen
2008-12-30 18:18 ` pv_ops dom0 kernel failure with ata_piix Pasi Kärkkäinen
2008-12-30 19:03 ` Pasi Kärkkäinen
2008-12-31 21:36 ` Jeremy Fitzhardinge
2009-01-02 6:44 ` Pasi Kärkkäinen
2009-01-09 17:40 ` Pasi Kärkkäinen
2009-01-09 21:01 ` Andrew Lyon
2009-01-22 19:46 ` pv_ops dom0 kernel failure with ata_piix / irq problems Pasi Kärkkäinen
2009-01-22 20:23 ` Jeremy Fitzhardinge
2009-01-24 14:09 ` Pasi Kärkkäinen
2009-01-24 14:58 ` Pasi Kärkkäinen
2009-01-24 18:58 ` Jeremy Fitzhardinge
2009-01-24 20:17 ` Pasi Kärkkäinen
2009-01-24 23:49 ` Pasi Kärkkäinen
2009-01-25 0:51 ` Pasi Kärkkäinen
2009-01-25 0:59 ` Jeremy Fitzhardinge
2009-01-25 11:28 ` Pasi Kärkkäinen
2009-01-30 18:12 ` Ian Campbell
2009-01-30 18:16 ` Ian Campbell
2009-01-30 18:50 ` Jeremy Fitzhardinge [this message]
2009-02-02 8:42 ` Pasi Kärkkäinen
2009-02-02 19:22 ` Pasi Kärkkäinen
2009-02-02 20:11 ` Pasi Kärkkäinen
2009-02-02 20:34 ` Pasi Kärkkäinen
2009-02-02 21:25 ` Pasi Kärkkäinen
2009-02-03 5:32 ` Jeremy Fitzhardinge
2009-02-03 6:16 ` Boris Derzhavets
2009-02-03 9:15 ` Pasi Kärkkäinen
2009-02-03 9:19 ` Pasi Kärkkäinen
2009-01-31 15:03 ` Attempt to compile 2.6.29-rc3 with pv_ops suppot for Dom0 Boris Derzhavets
2009-02-02 1:14 ` Jeremy Fitzhardinge
2009-02-02 9:53 ` Ian Campbell
2009-02-02 12:32 ` Boris Derzhavets
2009-02-02 12:42 ` Ian Campbell
2009-02-02 13:22 ` Boris Derzhavets
2009-02-02 14:04 ` Attempt to load 2.6.29-rc3 with pv_ops suppot for Dom0 under Xen 3.3.1 Hypervisor Boris Derzhavets
2009-02-02 14:40 ` Ian Campbell
2009-02-02 16:21 ` Boris Derzhavets
2009-02-02 17:32 ` Jeremy Fitzhardinge
2009-02-02 18:08 ` Boris Derzhavets
2009-02-02 22:43 ` Boris Derzhavets
2009-02-02 23:11 ` Jeremy Fitzhardinge
2009-02-03 6:00 ` Boris Derzhavets
2009-01-26 10:54 ` pv_ops dom0 kernel failure with ata_piix / irq problems Gerd Hoffmann
2009-01-26 12:47 ` Pasi Kärkkäinen
2009-01-24 23:10 ` Christophe Saout
2009-01-24 23:51 ` Pasi Kärkkäinen
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=49834C0B.1030309@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.lyon@gmail.com \
--cc=deshantm@gmail.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.