All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: Re: pv_ops parport trouble
Date: Thu, 19 Feb 2009 08:23:43 -0800	[thread overview]
Message-ID: <499D878F.4070906@goop.org> (raw)
In-Reply-To: <C5C33459.314B%keir.fraser@eu.citrix.com>

Keir Fraser wrote:
> On 19/02/2009 15:28, "Gerd Hoffmann" <kraxel@redhat.com> wrote:
>
>   
>> Note that IRQ 7 is *level* triggered and we have a bunch of *shared*
>> irqs which are *edge* triggered.  Given this I wonder my test box is
>> able to stay up that long.
>>     
>
> Yes, that looks completely backwards. Could pv_ops dom0 be getting the
> trigger flag in IO-APIC redir entries inverted somehow?
>   

I guess that's possible, but the code in question does just pass the 
trigger and polarity straight through.  What does it say about the 
trigger and polarity for those interrupts in the dmesg output?

I guess it would explain quite a few of the "lost interrupt" symptoms 
we've been seeing, but I'm surprised things work at all well if they 
really are reversed.

    J

  reply	other threads:[~2009-02-19 16:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19 14:38 pv_ops parport trouble Gerd Hoffmann
2009-02-19 15:28 ` Gerd Hoffmann
2009-02-19 16:07   ` Keir Fraser
2009-02-19 16:23     ` Jeremy Fitzhardinge [this message]
2009-02-19 16:31       ` Gerd Hoffmann
2009-02-19 16:37         ` Jeremy Fitzhardinge
2009-02-19 16:45           ` Gerd Hoffmann
2009-02-19 16:49             ` Jeremy Fitzhardinge
2009-02-19 16:56               ` Gerd Hoffmann
2009-02-19 17:11                 ` Keir Fraser
2009-02-19 16:51       ` Keir Fraser
2009-02-19 17:08         ` Jeremy Fitzhardinge

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=499D878F.4070906@goop.org \
    --to=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.com \
    --cc=kraxel@redhat.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.