All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ballabio_Dario@emc.com, manfred@colorfullife.com,
	warp@mercury.d2dc.net,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: eata irq abuse (was: Re: Linux 2.5.60)
Date: 12 Feb 2003 08:40:34 -0600	[thread overview]
Message-ID: <1045060838.1823.7.camel@mulgrave> (raw)
In-Reply-To: <20030212142541.A8262@infradead.org>

On Wed, 2003-02-12 at 08:25, Christoph Hellwig wrote:
> On Wed, Feb 12, 2003 at 09:13:10AM -0500, Ballabio_Dario@emc.com wrote:
> > Last time I tried to run the detect routine with interrupts enabled,
> > it just hung at the first occurrence on an inb() from
> > the board registers. If someone is able to have it 
> > working with interrupts enabled and qualifies the
> > solution on all the platforms and eata boards,
> > I'd be more than happy to remove it.
> 
> Ah, you don't need the lock but the disabled interrupts!

In general, that's not correct: most HBA registers have to be accessed
in sequence, thus you need global protection from anyone else touching
them while you're at the registers.  This is what host_lock was designed
for.

James



  reply	other threads:[~2003-02-12 14:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 14:13 eata irq abuse (was: Re: Linux 2.5.60) Ballabio_Dario
2003-02-12 14:25 ` Christoph Hellwig
2003-02-12 14:40   ` James Bottomley [this message]
2003-02-12 14:51     ` Christoph Hellwig
2003-02-12 14:54       ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2003-02-12 15:37 Ballabio_Dario
2003-02-12 12:47 Ballabio_Dario
2003-02-12 13:17 ` Christoph Hellwig
2003-02-12 10:08 Ballabio_Dario
2003-02-12 15:28 ` Jeff Garzik
2003-02-12 16:03   ` Jeff Garzik
2003-02-12 19:11     ` Suresh Kr N
2003-02-11 17:45 Manfred Spraul
2003-02-11 23:01 ` Zephaniah E. Hull

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=1045060838.1823.7.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=Ballabio_Dario@emc.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=warp@mercury.d2dc.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.