From: Bastian Blank <waldi@debian.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Fraser <keir.fraser@eu.citrix.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: pvops-2.6.32 - Interrupt routing problem
Date: Tue, 16 Mar 2010 09:18:32 +0100 [thread overview]
Message-ID: <20100316081832.GA20502@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <20100316013114.GD7622@phenom.dumpdata.com>
On Mon, Mar 15, 2010 at 09:31:14PM -0400, Konrad Rzeszutek Wilk wrote:
> 1) Can you boot your baremetal with these options:
> acpi.debug_level=0xffffffff acpi.debug_layer=0x2 apic=debug
| IOAPIC[0]: Set routing entry (8-14 -> 0x3e -> IRQ 14 Mode:0 Active:0)
| IOAPIC[0]: Set routing entry (8-14 -> 0x3e -> IRQ 14 Mode:1 Active:1)
> 2) And then later on your Xen with these (make SURE to _not_ have apic=debug on
> the Linux kernel command line with Xen, it will blow):
> xen.gz apic=debug apic_verbosity=debug console_to_ring sync_console loglvl=all guest_loglvl=all
| (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 Mode:0 Active:0)
| (XEN) Pin 8-14 already programmed
| (XEN) IOAPIC[0]: Set PCI routing entry (8-14 -> 0x88 -> IRQ 14 Mode:1 Active:1)
| (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0x38 -> IRQ 5 Mode:0 Active:0)
| (XEN) Pin 8-5 already programmed
| (XEN) IOAPIC[0]: Set PCI routing entry (8-5 -> 0x38 -> IRQ 5 Mode:1 Active:1)
Still with my hack to allow 8-5 and 8-14 to be reprogrammed.
Bastian
--
The heart is not a logical organ.
-- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4
next prev parent reply other threads:[~2010-03-16 8:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 11:19 pvops-2.6.32 - Interrupt routing problem Bastian Blank
2010-03-10 16:08 ` Ian Campbell
2010-03-10 16:19 ` Bastian Blank
2010-03-10 18:17 ` Jeremy Fitzhardinge
2010-03-10 20:32 ` Bastian Blank
2010-03-10 19:40 ` Ian Campbell
2010-03-10 20:00 ` Konrad Rzeszutek Wilk
2010-03-14 14:08 ` Bastian Blank
2010-03-14 15:23 ` Bastian Blank
2010-03-14 15:56 ` Jeremy Fitzhardinge
2010-03-14 16:17 ` Bastian Blank
2010-03-15 4:30 ` Zhang, Xiantao
2010-03-15 10:11 ` Bastian Blank
2010-03-15 10:36 ` Bastian Blank
2010-03-15 13:48 ` Zhang, Xiantao
2010-03-15 14:18 ` Bastian Blank
2010-03-15 14:38 ` Zhang, Xiantao
2010-03-15 21:15 ` Bastian Blank
2010-03-16 1:31 ` Konrad Rzeszutek Wilk
2010-03-16 8:18 ` Bastian Blank [this message]
2010-03-16 15:32 ` Konrad Rzeszutek Wilk
2010-03-16 18:20 ` Bastian Blank
2010-03-17 2:05 ` Konrad Rzeszutek Wilk
2010-03-19 11:39 ` Bastian Blank
2010-03-19 12:13 ` Bastian Blank
2010-03-21 21:47 ` Bastian Blank
2010-03-22 6:24 ` Jeremy Fitzhardinge
2010-03-23 11:37 ` Jan Beulich
2010-03-23 12:37 ` Bastian Blank
2010-03-23 14:04 ` Jan Beulich
2010-03-23 15:49 ` Bastian Blank
2010-03-19 14:15 ` Zhang, Xiantao
2010-03-19 14:36 ` Bastian Blank
2010-03-19 2:55 ` Zhang, Xiantao
2010-03-19 11:06 ` Bastian Blank
2010-03-14 16:41 ` Bastian Blank
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=20100316081832.GA20502@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--cc=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.zhang@intel.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 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).