public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: hwo to adjust interrupt?
Date: Mon, 15 Aug 2005 15:06:02 -0400	[thread overview]
Message-ID: <1124132762.5552.104.camel@localhost.localdomain> (raw)
In-Reply-To: <OF524C3938.82D78F5A-ON8825705E.00652E9F-8825705E.0067395D@us.ibm.com>

ic. thanks a lot for explanation.

so these are level sensitive interrupt.

i need to find a hw book now...

Ming

On Mon, 2005-08-15 at 11:47 -0700, Bryan Henderson wrote:
> >so it is possible that both card raise intr quicker than isr run, then
> >both isr will do mmio and go ahead, but then what is
> >
> >device 1 raise intr
> >device 2 isr run and not belong to it, so quit, but before it clear intr
> >and quit
> >device 2 raise intr
> >device 1 isr run and handle device 1, then clear intr and quit.
> >
> >then device 2 intr lost?
> 
> As these are level sensitive interrupt requests, they can't be lost.  As 
> long as Device 2 is requesting service,
> the shared IRQ is raised and at some point Linux will call Device 2's 
> interrupt handler.  Either the first level IRQ handler will keep calling 
> all the interrupt handlers that service that IRQ until the IRQ subsides, 
> or it will unmask the IRQ, causing an immediate new interrupt and the 
> first level interrupt handler runs again and calls all the device drivers 
> again.
> 
> The raised IRQ says, "Device 1 or Device 2 needs service."  The device 
> drivers clear the service request of the individual device; as long as 
> either device requests service, the IRQ is raised.
> 
> --
> Bryan Henderson                     IBM Almaden Research Center
> San Jose CA                         Filesystems
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2005-08-15 19:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 22:31 hwo to adjust interrupt? Ming Zhang
2005-08-12  7:14 ` Arjan van de Ven
2005-08-12 13:14   ` Ming Zhang
2005-08-12 16:59   ` Bryan Henderson
2005-08-12 17:04     ` Arjan van de Ven
2005-08-12 17:35       ` Bryan Henderson
2005-08-12 17:45         ` Ming Zhang
2005-08-12 17:51         ` Arjan van de Ven
2005-08-12 18:06           ` Ming Zhang
2005-08-15 18:47             ` Bryan Henderson
2005-08-15 19:06               ` Ming Zhang [this message]
2005-08-12 19:05         ` Ming Zhang
2005-08-12 19:14           ` Matthew Wilcox
2005-08-12 19:27             ` Ming Zhang

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=1124132762.5552.104.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=arjan@infradead.org \
    --cc=hbryan@us.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    /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