All of lore.kernel.org
 help / color / mirror / Atom feed
From: johannes@sipsolutions.net (Johannes Berg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm/mach-imx: use endian-safe readl/readw/writel/writew
Date: Mon, 25 Jan 2016 11:43:38 +0100	[thread overview]
Message-ID: <1453718618.2164.2.camel@sipsolutions.net> (raw)
In-Reply-To: <27961664.oTCXiXao1R@wuerfel>

On Sun, 2016-01-24 at 22:28 +0100, Arnd Bergmann wrote:
>?
> The patch looks fine to me, in the sense that we can safely assume
> that the behavior won't change for little-endian, and that it is
> fixing a bug for big-endian.
> 
> I would feel more comfortable with a patch using the non-relaxed()
> accessors though, as that can avoid a number of subtle bugs with
> I/O ordering.

I could easily generate this, obviously, the spatch was above :)

> Unfortunately, there is a nonzero overhead in the extra cache sync
> on the Cortex-A9 based platforms (most imx6), so this has to
> be done very carefully to avoid performance regressions. It's
> probably a good idea to keep the two changes as separate commits,
> but I'd also like to get both applied in the same merge window,
> as 'readl_relaxed' tends to say "I have proven that I don't need
> barriers", while the existing code just screams "I have no idea
> about what I'm doing here".

So does my patch, and I'm not sure I'm qualified to really judge which
ones need to be relaxed for performance reasons and which ones should
be changed.


johannes

      reply	other threads:[~2016-01-25 10:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 16:02 [PATCH 1/2] arm/mach-imx: use endian-safe readl/readw/writel/writew Johannes Berg
2016-01-24 16:02 ` [PATCH 2/2] arm/mach-imx: enable big endian mode Johannes Berg
2016-01-24 16:51   ` Arnd Bergmann
2016-01-24 21:28 ` [PATCH 1/2] arm/mach-imx: use endian-safe readl/readw/writel/writew Arnd Bergmann
2016-01-25 10:43   ` Johannes Berg [this message]

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=1453718618.2164.2.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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.