From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: "Moore, Eric" <Eric.Moore@lsi.com>,
Grant Grundler <grundler@google.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 1/11] mpt2sas: mpt2sas_base sources
Date: Tue, 03 Mar 2009 15:29:16 -0600 [thread overview]
Message-ID: <1236115756.15993.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20090225211224.GW16891@parisc-linux.org>
On Wed, 2009-02-25 at 14:12 -0700, Matthew Wilcox wrote:
> On Wed, Feb 25, 2009 at 01:27:00PM -0700, Moore, Eric wrote:
> > > > +static void
> > > > +_base_mask_interrupts(struct MPT2SAS_ADAPTER *ioc)
> > > > +{
> > > > + ? ? ? u32 him_register;
> > > > +
> > > > + ? ? ? ioc->mask_interrupts = 1;
> > > > + ? ? ? him_register = readl(&ioc->chip->HostInterruptMask);
> > > > + ? ? ? him_register |= MPI2_HIM_DIM + MPI2_HIM_RIM +
> > > MPI2_HIM_RESET_IRQ_MASK;
> > > > + ? ? ? writel(him_register, &ioc->chip->HostInterruptMask);
> > >
> > > This is a posted write. Does it need to be flushed?
> > > ie do other parts of the driver require this take effect immediately
> > > or will they tolerate some late arriving interrupt?
> >
> > What are you suggesting? Calling wmb()?
>
> PCI writes can be posted, so the him_register writel() may not complete
> for a few thousand cycles. wmb() isn't going to solve the problem. A
> readl() from the device would, as would your current solution of
> ignoring subsequent interrupts.
This seems to be the most serious issue with the current patch set. If
you repost with that fixed, I can put it into scsi-misc and we can
address the other issues later.
James
next prev parent reply other threads:[~2009-03-03 21:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 9:32 [PATCH 1/11] mpt2sas: mpt2sas_base sources Eric Moore
2009-02-25 0:00 ` Grant Grundler
2009-02-25 20:27 ` Moore, Eric
2009-02-25 21:12 ` Matthew Wilcox
2009-02-25 22:12 ` Moore, Eric
2009-03-03 18:33 ` Matthew Wilcox
2009-03-03 21:29 ` James Bottomley [this message]
2009-03-03 21:49 ` Matthew Wilcox
2009-03-04 0:29 ` Moore, Eric
2009-03-04 3:22 ` Rob Evers
2009-03-04 3:54 ` Matthew Wilcox
2009-03-03 22:37 ` Grant Grundler
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=1236115756.15993.23.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Eric.Moore@lsi.com \
--cc=grundler@google.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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