linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: strongly ordered comment on device memory in mmu.c
Date: Tue, 5 Jun 2012 00:59:29 +0100	[thread overview]
Message-ID: <20120604235929.GA29501@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAB9O=CMc7Lk0RCRL539qOGfx0nO6=JZp3gP1gL_HXvBzkxv3Ew@mail.gmail.com>

On Mon, Jun 04, 2012 at 03:16:31PM -0700, John Linn wrote:
> Hi,
> 
> We see that the following comment appears to be wrong in that the
> memory is device memory rather than strongly ordered memory.
> 
> ??????? [MT_DEVICE] = {?????????? /* Strongly ordered / ARMv6 shared device */
> 
> If it's really just a bad comment we'll do a patch, but I was
> wondering if there's more to it such that the comment is correct?

On pre-ARMv6, it's strongly ordered.  On post-ARMv6, it's "shared device".
The comment is accurate though possibly a little ambiguous; you're just
unaware of the history.

      reply	other threads:[~2012-06-04 23:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04 22:16 strongly ordered comment on device memory in mmu.c John Linn
2012-06-04 23:59 ` Russell King - ARM Linux [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=20120604235929.GA29501@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.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 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).