From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH + an old question] firewire: ohci: use memory barriers to order descriptor updates
Date: Tue, 27 Jul 2010 13:22:50 +0200 (CEST) [thread overview]
Message-ID: <tkrat.a624272002398548@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.21d3972644f46dc9@s5r6.in-berlin.de>
On 27 Jul, Stefan Richter wrote:
> 2. a write memory barrier between branch_address update and wake-up of
> the DMA unit by MMIO register write.
>
> This patch adds only barrier 1.
>
> Barrier 2 is implicit in writel() on most machines --- or at least I
> think it is. See this from arch/alpha/include/asm/io.h:
Typo, arch/x86/include/asm/io.h was meant.
> #define build_mmio_write(name, size, type, reg, barrier) \
> static inline void name(type val, volatile void __iomem *addr) \
> { asm volatile("mov" size " %0,%1": :reg (val), \
> "m" (*(volatile type __force *)addr) barrier); }
>
> build_mmio_write(writel, "l", unsigned int, "r", :"memory")
>
> Does this order the mmio write relative to previous memory writes?
--
Stefan Richter
-=====-==-=- -=== ==-==
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-07-27 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 11:20 Stefan Richter
2010-07-27 11:22 ` Stefan Richter [this message]
2010-07-28 7:28 ` Clemens Ladisch
2010-07-28 9:09 ` Stefan Richter
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=tkrat.a624272002398548@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®