public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: "Zhao, Forrest" <forrest.zhao@intel.com>
Cc: James.Smart@Emulex.Com, matthew@wil.cx,
	linux-scsi@vger.kernel.org, "Caushik,
	Ramesh" <ramesh.caushik@intel.com>,
	sdake@mvista.com
Subject: Re: One question about SCSI device hotplug
Date: Tue, 1 Mar 2005 22:57:52 -0600	[thread overview]
Message-ID: <20050302045752.GC20042@lists.us.dell.com> (raw)
In-Reply-To: <8126E4F969BA254AB43EA03C59F44E8401850062@pdsmsx404>

On Wed, Mar 02, 2005 at 12:47:46PM +0800, Zhao, Forrest wrote:
> < but the LLDD doesn't get an interrupt from the firmware on such
> events).
> 
> So you mean that when SCSI device is surprise-removed, HBA will not
> assert an interrupt to kernel? Even LLDD doesn't know the SCSI device is
> removed?

Exactly.  Some controllers know, and assert events up to their LLDD.
Jame's Emulex driver apparently does, perhaps this holds true for all
FC devices.

Some firmwares (LSI megaraid for sure, Adaptec SCSI I believe) don't.

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

  reply	other threads:[~2005-03-02  4:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02  4:47 One question about SCSI device hotplug Zhao, Forrest
2005-03-02  4:57 ` Matt Domsch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-02 15:51 James.Smart
2005-03-02  5:33 Zhao, Forrest
2005-03-02  3:40 Rajat  Jain, Noida
2005-03-01 16:35 James.Smart
2005-03-02  4:42 ` Matt Domsch
2005-03-01 15:20 Nagpure, Dinesh
2005-03-01  9:06 Zhao, Forrest
2005-03-01 14:46 ` Matthew Wilcox

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=20050302045752.GC20042@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=James.Smart@Emulex.Com \
    --cc=forrest.zhao@intel.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=ramesh.caushik@intel.com \
    --cc=sdake@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox