From: Bastian Blank <waldi@debian.org>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Fraser <keir.fraser@eu.citrix.com>,
Keir@wavehammer.waldi.eu.org
Subject: Re: pvops-2.6.32 - Interrupt routing problem
Date: Mon, 15 Mar 2010 11:11:26 +0100 [thread overview]
Message-ID: <20100315101126.GA24650@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <EB8593BCECAB3D40A8248BE0B6400A38464169F7@shzsmsx502.ccr.corp.intel.com>
On Mon, Mar 15, 2010 at 12:30:32PM +0800, Zhang, Xiantao wrote:
> Could you try the following patch ? Currently, the GSI 0-15 's polarity and trigger mode are determined by hypervisor, and maybe hypervisor and dom0 has no agreement to determin them. Just follow dom0's setting with this patch, and I think it maybe work for you.
No, it does not. mp_register_gsi also disallows reprogramming of already
setup IO-APIC entries. But if I force it with the following hack, it
works. So I would assume this a bug in the hypervisor to setup the GSI
without knowing anything about it.
Bastian
diff -r 4152a3ce90a7 xen/arch/x86/mpparse.c
--- a/xen/arch/x86/mpparse.c Thu Mar 11 17:40:35 2010 +0000
+++ b/xen/arch/x86/mpparse.c Mon Mar 15 11:09:27 2010 +0100
@@ -1143,5 +1143,5 @@
if ((1<<bit) & mp_ioapic_routing[ioapic].pin_programmed[idx]) {
Dprintk(KERN_DEBUG "Pin %d-%d already programmed\n",
mp_ioapic_routing[ioapic].apic_id, ioapic_pin);
+ if (mp_ioapic_routing[ioapic].apic_id == 8 && ioapic_pin == 14); else
return -EEXIST;
}
--
What kind of love is that? Not to be loved; never to have shown love.
-- Commissioner Nancy Hedford, "Metamorphosis",
stardate 3219.8
next prev parent reply other threads:[~2010-03-15 10:11 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 [this message]
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
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=20100315101126.GA24650@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--cc=Keir@wavehammer.waldi.eu.org \
--cc=jeremy@goop.org \
--cc=keir.fraser@eu.citrix.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).