LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sinan Kaya <okaya@codeaurora.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-parisc@vger.kernel.org, arnd@arndb.de,
timur@codeaurora.org, sulrich@codeaurora.org
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Helge Deller <deller@gmx.de>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] parisc: define stronger ordering for the default readX()
Date: Tue, 17 Apr 2018 10:13:28 -0400 [thread overview]
Message-ID: <38a1d4e3-cabe-6c39-4355-8d8111637382@codeaurora.org> (raw)
In-Reply-To: <1523957852.3250.9.camel@HansenPartnership.com>
Hi James,
>
> Perhaps if you gave an example of the actual problem you're trying to
> fix we could assess if it affects parisc.
Let me clarify myself here. Maybe, there is a better solution.
/* assign ownership */
desc->status = DEVICE_OWN;
/* notify device of new descriptors */
writel(DESC_NOTIFY, doorbell);
The difference between writel() and writel_relax() is writel() guarantees
memory transactions to be flushed to the device before the register write.
writel_relaxed() does not provide any guarantees about the memory and IO
operations.
Similarly, readl() provides following code to observe the DMA result while
readl_relaxed() does not provide this guarantee.
Ideally, you want to embed rmb() and wmb() into the writel() and readl()
to provide this guarantee.
PA-RISC doesn't seem to support neither one of the barrier types. If you are
familiar with the architecture, maybe you could guide us here.
Is __raw_writeX() enough to provide this guarantee for this architecture?
Sinan
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-04-17 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 4:08 [PATCH v2 1/2] parisc: define stronger ordering for the default writeX() Sinan Kaya
2018-04-17 4:08 ` [PATCH v2 2/2] parisc: define stronger ordering for the default readX() Sinan Kaya
2018-04-17 9:37 ` James Bottomley
2018-04-17 14:13 ` Sinan Kaya [this message]
2018-04-17 15:55 ` James Bottomley
2018-04-17 18:28 ` Sinan Kaya
2018-04-17 22:53 ` John David Anglin
2018-04-18 13:39 ` Sinan Kaya
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=38a1d4e3-cabe-6c39-4355-8d8111637382@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=arnd@arndb.de \
--cc=deller@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=sulrich@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=timur@codeaurora.org \
--subject='Re: [PATCH v2 2/2] parisc: define stronger ordering for the default readX()' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).