linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macqel.be>
To: linuxppc-dev@ozlabs.org
Subject: E500 linux : are the 64-bit GPRs context-switched ?
Date: Mon, 25 Feb 2008 15:47:22 +0100	[thread overview]
Message-ID: <20080225144722.GA5011@ingate.macqel> (raw)
In-Reply-To: <20080222095022.GA635@ingate.macqel>

Dear ppclinux gurus,

I have just compiled linux-2.6.24 for a MPC8540 target using a MPC8540
specific gcc.

After my first attempt using ARCH=ppc, leading to an infinity of messages :
"SPE used in kernel", I recompiled the whole kernel sources using
the default ARCH (ARCH=powerpc).  I now have a kernel that does not complain
about "SPE used in kernel", but user processes still crash ramdomly.

Searching around, I learned that the E500 GPR registers are 64-bits wide,
and gcc targetted for powerpc-linuxspe uses them sometimes.  In the other
PPC32 targets, those registers are 32-bits wide.

The specific E500 64-bit move instructions are `evstdd' and `evldd'.
I searched in the linux kernel sources (2.6.24) but did not find where
those GPR registers could be saved in 64-bit mode for context-switch.

Is there a patch pending somewhere to preserve the E500 GPR's in 64-bit mode
for context-switch ?

Philippe

  parent reply	other threads:[~2008-02-25 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080221123534.GA17716@ingate.macqel>
2008-02-22  9:50 ` MPC8540 : What's "SPE used in kernel" ? Philippe De Muyter
2008-02-22 15:29   ` Johannes Berg
2008-02-22 18:33   ` Andy Fleming
2008-02-23  9:24     ` Philippe De Muyter
2008-02-23  9:51       ` Johannes Berg
2008-02-23 10:17         ` Philippe De Muyter
2008-02-23 10:25           ` Johannes Berg
2008-02-26  7:39             ` Kumar Gala
2008-02-26 10:34               ` Philippe De Muyter
2008-02-25 14:47   ` Philippe De Muyter [this message]
2008-02-25 16:58     ` E500 linux : are the 64-bit GPRs context-switched ? Scott Wood

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=20080225144722.GA5011@ingate.macqel \
    --to=phdm@macqel.be \
    --cc=linuxppc-dev@ozlabs.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).