From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc mpc85xx: Do not protect TLB entry for debuggging in AS1 against invalidation
Date: Fri, 7 Sep 2012 14:50:08 -0500 [thread overview]
Message-ID: <504A4FF0.3010208@freescale.com> (raw)
In-Reply-To: <6670B5959A1255459E98630A607295B473CC2B@hrsrv31.haslerrail.net>
On 09/07/2012 07:50 AM, Joye Laurent wrote:
> In case of booting from RAM (CONFIG_SYS_RAMBOOT), a TLB entry is created
> for IVPR + IVOR15 to map on valid OP code address.
> This TLB entry shall not be protected against invalidation, because
> a new TLB entry to access RAM in AS0 will be created by
> cpu_init_early_f.
> If this TLB entry is protected against invalidation, this will creates
> 2 TLB for the same address range (forbidden).
Instead we should explicitly remove the debug TLB when it is no longer
needed.
-Scott
prev parent reply other threads:[~2012-09-07 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 12:50 [U-Boot] [PATCH] powerpc mpc85xx: Do not protect TLB entry for debuggging in AS1 against invalidation Joye Laurent
2012-09-07 19:50 ` Scott Wood [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=504A4FF0.3010208@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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