xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: pvops-2.6.32 - Interrupt routing problem
Date: Mon, 15 Mar 2010 11:36:22 +0100	[thread overview]
Message-ID: <20100315103622.GA25174@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <20100315101126.GA24650@wavehammer.waldi.eu.org>

On Mon, Mar 15, 2010 at 11:11:26AM +0100, Bastian Blank wrote:
> 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.

Or are they pre-programmed by the BIOS?

IO-APIC info from Xen now:
(XEN) IO APIC #8......
(XEN) .... register #00: 08000000
(XEN) .......    : physical APIC id: 08
(XEN) .......    : Delivery Type: 0
(XEN) .......    : LTS          : 0
(XEN) .... register #01: 000F0011
(XEN) .......     : max redirection entries: 000F
(XEN) .......     : PRQ implemented: 0
(XEN) .......     : IO APIC version: 0011
(XEN) .... register #02: 08000000
(XEN) .......     : arbitration: 08
(XEN) .... IRQ redirection table:
(XEN)  NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
(XEN)  00 000 00  1    0    0   0   0    0    0    00
(XEN)  01 000 00  0    0    0   0   0    0    0    28
(XEN)  02 000 00  0    0    0   0   0    0    0    F0
(XEN)  03 000 00  0    0    0   0   0    0    0    30
(XEN)  04 000 00  0    0    0   0   0    0    0    F1
(XEN)  05 000 00  1    0    0   0   0    0    0    38
(XEN)  06 000 00  1    0    0   0   0    0    0    40
(XEN)  07 000 00  1    0    0   0   0    0    0    48
(XEN)  08 000 00  0    0    0   0   0    0    0    50
(XEN)  09 000 00  0    0    0   0   0    0    0    58
(XEN)  0a 000 00  1    0    0   0   0    0    0    60
(XEN)  0b 000 00  1    0    0   0   0    0    0    68
(XEN)  0c 000 00  0    0    0   0   0    0    0    70
(XEN)  0d 000 00  1    0    0   0   0    0    0    78
(XEN)  0e 00A 0A  0    1    0   1   0    0    0    9A
(XEN)  0f 000 00  1    0    0   0   0    0    0    90

If I read the code correctly, the 1 in the trigger line means level
triggered. But the Linux kernel still lists it as edge triggered.

Bastian

-- 
	"We have the right to survive!"
	"Not by killing others."
		-- Deela and Kirk, "Wink of An Eye", stardate 5710.5

  reply	other threads:[~2010-03-15 10:36 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 [this message]
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=20100315103622.GA25174@wavehammer.waldi.eu.org \
    --to=waldi@debian.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).