All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Chris Friesen <chris.friesen@genband.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org,
	Scott Wood <scottwood@freescale.com>,
	timur@freescale.com
Subject: Re: linux support for freescale e5500 core?
Date: Fri, 17 Sep 2010 02:39:44 -0500	[thread overview]
Message-ID: <4737649C-42E5-47EC-8839-314820EAE45E@kernel.crashing.org> (raw)
In-Reply-To: <4C930C55.5030008@genband.com>


On Sep 17, 2010, at 1:36 AM, Chris Friesen wrote:

> On 09/16/2010 11:33 PM, Benjamin Herrenschmidt wrote:
>> On Fri, 2010-09-17 at 00:17 -0500, Kumar Gala wrote:
>>> Not sure how the 970 bit worked, but this seems a bit problematic =
for
>>> switching between kernel and application for how we do this on
>>> e500mc/e5500.  We'd have to touch the control bit on every exception
>>> path which seems ugly to me.
>>=20
>> Unless the kernel uses dcbzl (feature fixup replacement ?)
>>=20
>> In that case it's on context switch only.
>=20
> This is basically what we did.  Kernel and system libraries (glibc and
> friends) always use dcbzl, process flag indicates compatibility, touch
> the control bit on task context switch if the prev and next processes
> have different compatibility modes.
>=20
> On the 970 you have to invalidate the entire icache whenever you =
change
> the control bit.  This is a pain involving a loop that calls icbi on =
512
> cachelines.

I'm pretty sure on e500mc / e5500 you only need proper sync/isync/msync =
after the change in the control register.

- k=

      reply	other threads:[~2010-09-17  7:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 20:06 linux support for freescale e5500 core? Chris Friesen
2010-09-16 21:39 ` Scott Wood
2010-09-16 21:44   ` Chris Friesen
2010-09-16 22:03     ` Benjamin Herrenschmidt
2010-09-16 22:26       ` Chris Friesen
2010-09-17  0:03         ` Benjamin Herrenschmidt
2010-09-17  5:17           ` Kumar Gala
2010-09-17  5:33             ` Benjamin Herrenschmidt
2010-09-17  6:36               ` Chris Friesen
2010-09-17  7:39                 ` Kumar Gala [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=4737649C-42E5-47EC-8839-314820EAE45E@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=chris.friesen@genband.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=scottwood@freescale.com \
    --cc=timur@freescale.com \
    /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.