From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/mm: Add translation mode information in /proc/cpuinfo
Date: Wed, 22 Feb 2017 19:03:01 +1100 [thread overview]
Message-ID: <1487750581.23576.217.camel@kernel.crashing.org> (raw)
In-Reply-To: <8ec533a5-daf6-4644-ffea-e940fe3e77f9@linux.vnet.ibm.com>
On Wed, 2017-02-22 at 11:19 +0530, Aneesh Kumar K.V wrote:
> I avoided using MMU, because it will confuse hardware guys.
Why would it ? I don't see how anybody would be confused. And they
aren't the primary consumers of /proc/cpuinfo anyway. I agree with
Michal here.
> Radix is not
> clearly the full definition of
> Memory management unit, but rather the translation mode used by memory
> management unit. But
> i don't have strong opinion on this.
Who cares ? People understand :-) If you want call it "MMU Mode: if you
think it's cleared but I don't like too much having a space on the left
in case of stupid parsers...
> Do you want me to send an updated patch ? or you can update it when you
> apply it to your tree ?
>
> -aneesh
next prev parent reply other threads:[~2017-02-22 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 10:17 [PATCH] powerpc/mm: Add translation mode information in /proc/cpuinfo Aneesh Kumar K.V
2017-02-22 0:23 ` Balbir Singh
2017-02-22 5:45 ` Michael Ellerman
2017-02-22 5:49 ` Aneesh Kumar K.V
2017-02-22 8:03 ` Benjamin Herrenschmidt [this message]
2017-02-27 9:56 ` Michael Ellerman
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=1487750581.23576.217.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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.