linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Philippe De Muyter <phdm@macqel.be>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: MPC8540 : What's "SPE used in kernel" ?
Date: Fri, 22 Feb 2008 16:29:11 +0100	[thread overview]
Message-ID: <1203694151.7082.37.camel@johannes.berg> (raw)
In-Reply-To: <20080222095022.GA635@ingate.macqel>

[-- Attachment #1: Type: text/plain, Size: 502 bytes --]


> I wonder why a kernel configured for E500 and compiled by a E500-specific gcc
> triggers this message.  Is it invalid to use SPE instructions in the kernel 
> or do I misunderstand the message ?

I think it's like floating point/altivec, we don't always save the FP
registers on kernel/userspace transitions and so have to explicitly save
them to use them in the kernel, otherwise we'd clobber the userspace
register state.

I guess there's something like kernel_enter_spe()?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2008-02-22 15:29 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 [this message]
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   ` E500 linux : are the 64-bit GPRs context-switched ? Philippe De Muyter
2008-02-25 16:58     ` 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=1203694151.7082.37.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=phdm@macqel.be \
    /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).