From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] apic fail
Date: Mon, 19 Jul 2010 17:55:29 -0400 [thread overview]
Message-ID: <d5d30dc1d9b5a46fc20b2c9e42bde095@coraid.com> (raw)
In-Reply-To: <b414d15ec9d2f06eea9485afa5d0e732@terzarima.net>
On Mon Jul 19 17:26:13 EDT 2010, forsyth@terzarima.net wrote:
> >Is one interrupt being dispatched to two cpus, I wonder?
>
> even so, that should be fine, but ether8169.c doesn't seem to make much use of the rlock it declares.
really? i thought a bedrock assumption of pci interrupts is
that once an interrupt vector is asserted, it can't reassert until
the os has acked that vector with EOI.
it may be that the same interrupt source is mapped to different
vectors on the different processors. that would be an interesting
world to live in.
- erik
next prev parent reply other threads:[~2010-07-19 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 20:14 Richard Miller
2010-07-19 21:25 ` Charles Forsyth
2010-07-19 21:55 ` erik quanstrom [this message]
2010-07-20 8:54 ` Richard Miller
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=d5d30dc1d9b5a46fc20b2c9e42bde095@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.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 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).