From: Jon Smirl <jonsmirl@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net,
Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
ian.pratt@cl.cam.ac.uk
Subject: Re: Interrupt forwarding
Date: Sat, 12 Mar 2005 13:59:15 -0500 [thread overview]
Message-ID: <9e4733910503121059305b4c3f@mail.gmail.com> (raw)
In-Reply-To: <f7ad8bba837b5b01bf13f789a612118f@cl.cam.ac.uk>
On Sat, 12 Mar 2005 18:48:53 +0000, Keir Fraser
<Keir.Fraser@cl.cam.ac.uk> wrote:
> We don't go that far. A sensible approach would be to require the
> driver to be restarted, and to reset the hardware device, before
> unmasking. Or to rate limit each interrupt line to an
Have you tried cycling the cards to suspend S0 (power off) as a way of
clearing the interrupt?
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-12 18:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 18:11 Interrupt forwarding Ian Pratt
2005-03-12 18:21 ` Keir Fraser
2005-03-12 18:33 ` Jon Smirl
2005-03-12 18:48 ` Keir Fraser
2005-03-12 18:53 ` Jon Smirl
2005-03-12 18:59 ` Jon Smirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-12 19:59 Ian Pratt
2005-03-12 20:07 ` Jon Smirl
2005-03-13 10:01 ` Keir Fraser
2005-03-13 15:56 ` Jon Smirl
2005-03-13 16:01 ` Keir Fraser
2005-03-13 16:49 ` Jon Smirl
2005-03-12 18:02 Jon Smirl
2005-03-12 18:12 ` Mark Williamson
2005-03-14 15:39 ` Ronald G. Minnich
2005-03-14 15:44 ` Mark Williamson
2005-03-14 16:01 ` Ronald G. Minnich
2005-03-14 16:04 ` Ronald G. Minnich
2005-03-14 21:59 ` Andi Kleen
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=9e4733910503121059305b4c3f@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.