xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bastian Blank <waldi@debian.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Cc: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: pvops-2.6.32 - Interrupt routing problem
Date: Sun, 14 Mar 2010 15:08:14 +0100	[thread overview]
Message-ID: <20100314140813.GA5309@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <20100310111923.GA7087@wavehammer.waldi.eu.org>

On Wed, Mar 10, 2010 at 12:19:23PM +0100, Bastian Blank wrote:
> I was able to test Xen 3.4.3-rc3 and the current 2.6.32 tree on a
> HP DL385 G6.

It also happens with Xen 4.0.0-rc6.

However something caught my attention.

> |  5: xen-pirq-ioapic-edge  ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb4
> [    1.626062] ehci_hcd 0000:00:07.2: PCI INT A -> Link[IUSB] -> GSI 5 (level, low) -> IRQ 5

> | 14: xen-pirq-ioapic-edge  sata_svw
> [    1.718903] sata_svw 0000:01:0e.0: PCI INT A -> Link[ISF0] -> GSI 14 (level, low) -> IRQ 14

The interrupts are enabled as edge driven, but are reported by ACPI as
level triggered.

Bastian

-- 
There are certain things men must do to remain men.
		-- Kirk, "The Ultimate Computer", stardate 4929.4

  parent reply	other threads:[~2010-03-14 14:08 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 [this message]
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
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=20100314140813.GA5309@wavehammer.waldi.eu.org \
    --to=waldi@debian.org \
    --cc=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.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 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).