All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v3] updates to qbman (soc drivers) to support arm/arm64
Date: Tue, 27 Jun 2017 10:10:07 +0100	[thread overview]
Message-ID: <20170627091006.GN4902@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CAK8P3a0N5tiP7RPMg=Q8fsROuYabJjQ5Awd2ekrn686nDqdNwA@mail.gmail.com>

On Tue, Jun 27, 2017 at 11:05:38AM +0200, Arnd Bergmann wrote:
> On Tue, Jun 27, 2017 at 10:17 AM, Russell King - ARM Linux
> <linux@armlinux.org.uk> wrote:
> > On Tue, Jun 27, 2017 at 09:17:48AM +0200, Arnd Bergmann wrote:
> >> I'd suggest we start out by converting this to some standard API
> >> first, regardless of performance, to get it working properly with code
> >> that should be maintainable at least, and make progress with your
> >> hardware enablement.
> >
> > I think Roy is rather confused right now about what the driver does
> > and doesn't do.
> >
> > With his patches, two areas are mapped on ARM:
> >
> > 1. The addr.ci area is mapped using ioremap().  This is a device mapping,
> >    and is used by the "Cache-inhibited register access." functions.
> >
> > 2. The addr.ce area is mapped using ioremap_wc(), and all other stuff
> >    including the verb accesses go through this region.  This is a
> >    memory, non-cacheable mapping.
> >
> > The addr.ce region is the area that has a mixture of memset(), MMIO
> > accessors, direct CPU accesses, cache flushes and prefetches used on
> > it.
> >
> > As it is marked non-cacheable, the cache flushes are a pure waste of
> > CPU cycles.  Prefetching to a non-cacheable area doesn't make much
> > sense either.
> >
> > So, I think for ARM: just kill the cache flushing - its doing nothing
> > useful.  The prefetching could also be removed as well to recover a
> > few more CPU cycles.
> 
> Right, that sounds good. I wondered about the ioremap_wc() earlier
> and thought I must have missed something as it didn't make any sense
> to me, but apparently that was because the code really doesn't make
> sense ;-).
> 
> It would be good to get consistent __iomem annotations on it too,
> so we can see exactly where the MMIO interfaces are used incorrectly,
> and find a fix for that.
> 
> I wonder if doing memcpy_toio on the write-combining mapping
> will do what Roy wants and and up sending a single bus transaction
> for one descriptor most of the time, while fitting in with the ioremap_wc()
> interface and its __iomem pointers.

Either the CE region needs __iomem pointers and proper accessors, or
it needs to be using memremap(offset, size, MEMREMAP_WC) and not use
the iomem accessors.

The CI region should definitely have __iomem annotations though.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2017-06-27  9:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20 17:27 [GIT PULL v3] updates to qbman (soc drivers) to support arm/arm64 Leo Li
2017-06-23 14:56 ` Arnd Bergmann
2017-06-23 15:22   ` Mark Rutland
2017-06-23 15:55     ` Russell King - ARM Linux
2017-06-23 16:23       ` Mark Rutland
2017-06-23 19:39       ` Roy Pledge
2017-06-23 18:58     ` Roy Pledge
2017-06-24 12:10       ` Russell King - ARM Linux
2017-06-27 18:36         ` Roy Pledge
2017-06-27  7:17       ` Arnd Bergmann
2017-06-27  8:17         ` Russell King - ARM Linux
2017-06-27  9:05           ` Arnd Bergmann
2017-06-27  9:10             ` Russell King - ARM Linux [this message]
2017-06-27 10:35               ` Arnd Bergmann
2017-06-27 19:03                 ` Roy Pledge
2017-06-27 18:59         ` Roy Pledge
2017-06-23 15:38   ` Russell King - ARM Linux
2017-06-23 19:25     ` Roy Pledge

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=20170627091006.GN4902@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.