From: Matthew Wilcox <matthew@wil.cx>
To: Rob Evers <revers@redhat.com>
Cc: "Moore, Eric" <Eric.Moore@lsi.com>,
James Bottomley <James.Bottomley@HansenPartnership.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, 3 Mar 2009 20:54:47 -0700 [thread overview]
Message-ID: <20090304035447.GA1884@parisc-linux.org> (raw)
In-Reply-To: <49ADF402.4050504@redhat.com>
On Tue, Mar 03, 2009 at 10:22:42PM -0500, Rob Evers wrote:
> >(1) Add readl following writel from the function that disables interrupts
>
> Is a memory barrier required after the writel and before the readl to
> ensure that the writel executes before the readl on processors other than
> x86_64 and ia32?
No. Architectures such as PowerPC and Altix which have the potential
to issue writes out of order wrt io memory are required to implement
barriers in their writel() implementation.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-03-04 3:55 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
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 [this message]
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=20090304035447.GA1884@parisc-linux.org \
--to=matthew@wil.cx \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=grundler@google.com \
--cc=linux-scsi@vger.kernel.org \
--cc=revers@redhat.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