From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
"Steven J. Hill" <Steven.Hill@imgtec.com>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
Florian Fainelli <florian@openwrt.org>
Subject: Re: [PATCH v2] Revert "MIPS: make CAC_ADDR and UNCAC_ADDR account for PHYS_OFFSET"
Date: Wed, 26 Jun 2013 16:47:15 -0700 [thread overview]
Message-ID: <51CB7D83.4030904@imgtec.com> (raw)
In-Reply-To: <alpine.LFD.2.03.1306262233250.32101@linux-mips.org>
On 06/26/2013 02:41 PM, Maciej W. Rozycki wrote:
> Ralf,
> To complete the image, there is a set of new memory access instructions
> added (including but not limited to CACHE) that in the kernel mode
> separates accesses to the user space from accesses to the kernel space,
> i.e. the same virtual address can map differently depending on which
> instruction set it is used with. I encourage you to have at least a skim
> over the most recent set of MIPS architecture manuals publicly available
> where it all is documented.
>
> Maciej
Look into http://www.mips.com/auth/MD00091-2B-MIPS64PRA-AFP-03.52.pdf
(registration required). Read sections 4.13, 4.12 and 9.13-9.15.
Ignore anything for 64bit core.
Sorry, I asked David Lau to update MIPS32 actual docs but it can take time.
Right now it is from 2011 year.
- Leonid.
next prev parent reply other threads:[~2013-06-26 23:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 15:36 [PATCH v2] Revert "MIPS: make CAC_ADDR and UNCAC_ADDR account for PHYS_OFFSET" Steven J. Hill
2013-06-26 14:52 ` Ralf Baechle
2013-06-26 15:34 ` Steven J. Hill
2013-06-26 15:34 ` Steven J. Hill
2013-06-26 15:43 ` Leonid Yegoshin
2013-06-26 16:23 ` Ralf Baechle
2013-06-26 16:50 ` Leonid Yegoshin
2013-06-26 17:50 ` Ralf Baechle
2013-06-26 19:03 ` Leonid Yegoshin
2013-06-26 21:41 ` Maciej W. Rozycki
2013-06-26 23:47 ` Leonid Yegoshin [this message]
2013-07-03 14:01 ` Markos Chandras
2013-07-03 15:56 ` Steven J. Hill
2013-07-03 15:56 ` Steven J. Hill
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=51CB7D83.4030904@imgtec.com \
--to=leonid.yegoshin@imgtec.com \
--cc=Steven.Hill@imgtec.com \
--cc=florian@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.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.