From: Jesper Krogh <jesper@krogh.cc>
To: "Kashyap, Desai" <kashyap.desai@lsi.com>
Cc: linux-scsi@vger.kernel.org,
James.Bottomley@HansenPartnership.com, Eric.Moore@lsi.com,
Sathya.Prakash@lsi.com
Subject: Re: [PATCH 2/6] mpt fusion: Firmware Event implementation using seperate WorkQueue
Date: Mon, 06 Apr 2009 10:44:10 +0200 [thread overview]
Message-ID: <49D9C0DA.6000908@krogh.cc> (raw)
In-Reply-To: <20090403115025.GC17721@lsi.com>
Kashyap, Desai wrote:
> 1) Now Firmware events are handled by firmware event queue.
> Previously it was handled in interrupt context/WorkQueue of Linux.
> Firmware Event handling is restructured and optimized.
> 2.) Test Unit Ready will be used by driver to make sure device is
> already come up before indicating Device Add to Scsi subsystem.
Quick question.. are these changes (in 2.6.29) related to this one i got
only on 2.6.29:
[248240.137978] Pid: 9225, comm: mdrun_mpi.openm Not tainted 2.6.29 #30
[248240.137978] Call Trace:
[248240.137978] <IRQ> [<ffffffff8027231e>] __report_bad_irq+0x1e/0x80
[248240.137978] [<ffffffff80272502>] note_interrupt+0x182/0x1d0
[248240.137978] [<ffffffff80272f69>] handle_fasteoi_irq+0x89/0xe0
[248240.137978] [<ffffffff8020e73e>] do_IRQ+0x7e/0x110
[248240.137978] [<ffffffff8020cc93>] ret_from_intr+0x0/0xa
[248240.137978] <EOI> <3>handlers:
[248240.137978] [<ffffffffa014c920>] (mpt_interrupt+0x0/0x5f0 [mptbase])
[248240.290859] Disabling IRQ #19
--
Jesper
next prev parent reply other threads:[~2009-04-06 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 11:50 [PATCH 2/6] mpt fusion: Firmware Event implementation using seperate WorkQueue Kashyap, Desai
2009-04-03 18:21 ` James Bottomley
2009-04-06 8:17 ` Desai, Kashyap
2009-04-06 14:45 ` James Bottomley
2009-04-07 13:48 ` Desai, Kashyap
2009-04-07 15:46 ` James Bottomley
2009-04-06 8:44 ` Jesper Krogh [this message]
2009-04-06 9:06 ` Desai, Kashyap
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=49D9C0DA.6000908@krogh.cc \
--to=jesper@krogh.cc \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Sathya.Prakash@lsi.com \
--cc=kashyap.desai@lsi.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