From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Muli Ben-Yehuda <muli@il.ibm.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] aic94xx: fix SMP request DMA direction
Date: Sun, 30 Sep 2007 00:13:55 -0700 [thread overview]
Message-ID: <20070930071355.GC21125@tree.beaverton.ibm.com> (raw)
In-Reply-To: <46FDEFDD.8070401@garzik.org>
On Sat, Sep 29, 2007 at 02:25:33AM -0400, Jeff Garzik wrote:
> Muli Ben-Yehuda wrote:
>> On Fri, Sep 28, 2007 at 04:55:34PM -0700, Darrick J. Wong wrote:
>>> On Thu, Sep 27, 2007 at 10:33:41PM -0400, Jeff Garzik wrote:
>>>> Unless I'm missing something, the SMP request goes /to/ the PCI device
>>>> :)
>>>>
>>>> Signed-off-by: Jeff Garzik <jeff@garzik.org>
>>> ACK; builds ok and SMP commands seem to work ok (not that they
>>> didn't before).
>> Could this explain some weirdness we were seeing with aic94xx and
>> Calgary/CalIOC2 enabled, or are SMP commands not likely to be used in
>> normal operation? We map the IOMMU entries differently for FROMDEVICE
>> (RW) and TODEVICE(RO).
>
> SMP == scsi management == not used during normal data transfer.
>
> It could certainly explain flakiness if you have expanders, though
Actually, SMP commands are used during device discovery to find things
attached to expanders, so it seems likely that "it blows up almost
immediately after loading the module" symptoms are a result of this bug.
That said, the bug that Jeff fixed resulted in extra permissions (+w)
being set for the SMP request buffer, so that's probably why I've never
seen any problems manifesting on x260/x3800 systems.
(Unless the CalIOC2 has a write only mode?)
--D
next prev parent reply other threads:[~2007-09-30 7:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 2:33 [PATCH] aic94xx: fix SMP request DMA direction Jeff Garzik
2007-09-28 23:55 ` Darrick J. Wong
2007-09-29 6:22 ` Muli Ben-Yehuda
2007-09-29 6:25 ` Jeff Garzik
2007-09-30 7:13 ` Darrick J. Wong [this message]
2007-09-30 7:26 ` Muli Ben-Yehuda
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=20070930071355.GC21125@tree.beaverton.ibm.com \
--to=djwong@us.ibm.com \
--cc=jeff@garzik.org \
--cc=linux-scsi@vger.kernel.org \
--cc=muli@il.ibm.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