From: Arnd Bergmann <arnd@arndb.de>
To: Casey Leedom <leedom@chelsio.com>
Cc: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Toshi Kani" <toshi.kani@hp.com>,
"Andy Lutomirski" <luto@amacapital.net>,
"Juergen Gross" <jgross@suse.com>,
"Tomi Valkeinen" <tomi.valkeinen@ti.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
linux-fbdev <linux-fbdev@vger.kernel.org>,
"Suresh Siddha" <sbsiddha@gmail.com>,
"Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Dave Airlie" <airlied@redhat.com>,
"Antonino Daplas" <adaplas@gmail.com>,
"Jean-Christophe Plagniol-Villard" <plagnioj@jcrosoft.com>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"venkatesh.pallipadi@intel.com" <venkatesh.pallipadi@intel.com>,
"Stefan Bader" <stefan.bader@canonical.com>,
"Ville Syrjälä" <syrjala@sci.fi>, "Mel Gorman" <mgorman@suse.de>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Borislav Petkov" <bp@suse.de>,
"Davidlohr Bueso" <dbueso@suse.de>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"David Vrabel" <david.vrabel@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH v7 5/9] PCI: Add pci_iomap_wc() variants
Date: Thu, 25 Jun 2015 22:44:07 +0200 [thread overview]
Message-ID: <6806026.xb91q6Ad7G@wuerfel> (raw)
In-Reply-To: <4985EFDD773FCB459EF7915D2A3621ADC02F10@nice.asicdesigners.com>
On Thursday 25 June 2015 15:01:56 Casey Leedom wrote:
>
> Is there a reference I can read on this so I can understand
> when and where we can use the __raw_*() APIs? Can these
> Raw Read/Write operations be reordered with respect to
> each other or are the use of the various flavors of SYNC
> instructions just to maintain order between Cached Memory
> Accesses and I/O Instructions?
The interpretation is not consistent across architectures.
My best description would be that the __raw_*() accessors should
only be used for accessing RAM areas that are known to have no
side-effects and can be read in any size (8-bit to 64-bit wide),
any alignment, and do not have a specific endianess.
If you are dealing with MMIO registers that have a fixed endianess
and size, the correct accessor would be readl_relaxed(), which
is like readl() but lacks the barriers on certain architectures.
Arnd
next prev parent reply other threads:[~2015-06-25 20:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 22:08 [PATCH v7 0/9] pci: add pci_iomap_wc() and pci_ioremap_wc_bar() Luis R. Rodriguez
2015-06-19 22:08 ` [PATCH v7 1/9] pci: add pci_ioremap_wc_bar() Luis R. Rodriguez
2015-06-19 22:08 ` [PATCH v7 2/9] video: fbdev: i740fb: use arch_phys_wc_add() and pci_ioremap_wc_bar() Luis R. Rodriguez
2015-06-19 22:08 ` [PATCH v7 3/9] video: fbdev: kyrofb: " Luis R. Rodriguez
2015-06-19 22:08 ` [PATCH v7 4/9] video: fbdev: gxt4500: use pci_ioremap_wc_bar() for framebuffer Luis R. Rodriguez
2015-06-19 22:08 ` [PATCH v7 5/9] PCI: Add pci_iomap_wc() variants Luis R. Rodriguez
2015-06-23 22:42 ` Benjamin Herrenschmidt
2015-06-24 16:38 ` Luis R. Rodriguez
2015-06-24 22:05 ` Benjamin Herrenschmidt
2015-06-24 22:29 ` Luis R. Rodriguez
2015-06-24 23:38 ` Benjamin Herrenschmidt
2015-06-25 0:08 ` Luis R. Rodriguez
2015-06-25 0:52 ` Benjamin Herrenschmidt
2015-06-25 0:58 ` [Xen-devel] " Luis R. Rodriguez
2015-06-25 1:12 ` Benjamin Herrenschmidt
2015-06-25 15:01 ` Casey Leedom
2015-06-25 20:44 ` Arnd Bergmann [this message]
2015-06-25 21:40 ` Casey Leedom
2015-06-25 22:51 ` Benjamin Herrenschmidt
2015-06-26 19:31 ` Luis R. Rodriguez
2015-06-26 22:04 ` Benjamin Herrenschmidt
[not found] ` <CAB=NE6XwczF6FYXV=RHyK=7ikVk_tGp+h9ouWPyORNENq4+=Kw@mail.gmail.com>
2015-06-26 23:54 ` [Xen-devel] " Benjamin Herrenschmidt
2015-06-27 1:16 ` Luis R. Rodriguez
2015-06-26 2:02 ` Benjamin Herrenschmidt
2015-06-26 16:24 ` Casey Leedom
2015-06-26 22:00 ` Benjamin Herrenschmidt
2015-07-02 18:49 ` Luis R. Rodriguez
2015-07-02 22:26 ` Benjamin Herrenschmidt
2015-07-03 0:14 ` Casey Leedom
2015-06-19 22:08 ` [PATCH v7 6/9] lib: devres: add pcim_iomap_wc() variants Luis R. Rodriguez
2015-06-19 22:08 ` [PATCH v7 7/9] video: fbdev: arkfb: use arch_phys_wc_add() and pci_iomap_wc() Luis R. Rodriguez
2015-06-19 22:08 ` [PATCH v7 8/9] video: fbdev: s3fb: " Luis R. Rodriguez
2015-06-19 22:08 ` [PATCH v7 9/9] video: fbdev: vt8623fb: " Luis R. Rodriguez
2015-06-23 10:53 ` [PATCH v7 0/9] pci: add pci_iomap_wc() and pci_ioremap_wc_bar() Arnd Bergmann
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=6806026.xb91q6Ad7G@wuerfel \
--to=arnd@arndb.de \
--cc=adaplas@gmail.com \
--cc=airlied@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=daniel.vetter@ffwll.ch \
--cc=dave.hansen@linux.intel.com \
--cc=david.vrabel@citrix.com \
--cc=dbueso@suse.de \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=leedom@chelsio.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@suse.com \
--cc=mgorman@suse.de \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=plagnioj@jcrosoft.com \
--cc=roger.pau@citrix.com \
--cc=sbsiddha@gmail.com \
--cc=stefan.bader@canonical.com \
--cc=syrjala@sci.fi \
--cc=tglx@linutronix.de \
--cc=tomi.valkeinen@ti.com \
--cc=toshi.kani@hp.com \
--cc=vbabka@suse.cz \
--cc=venkatesh.pallipadi@intel.com \
--cc=ville.syrjala@linux.intel.com \
--cc=xen-devel@lists.xensource.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