From: Michael Neuling <mikey@neuling.org>
To: "Morrison, Tom" <tmorrison@empirix.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: MSR_SPE - being turned off...
Date: Tue, 05 May 2009 14:17:42 +1000 [thread overview]
Message-ID: <23583.1241497062@neuling.org> (raw)
In-Reply-To: <BD261180E6D35F4D9D32F3E44FD3D90110C30B99@EMPBEDEX.empirix.com>
> I have both a MPC8548 SBC and MPC8572 system that are running different
> flavors of the same Linux - 2.6.23.
>
> I explicitly am turning it on very early on.
Where are you turning this on? In the appication?
> Later, I have an application that is compiled with SPE instructions
> (e.g.: evstdd) , and there is where the problems happen.
What is the problem?
> If I explicitly make sure there are NO SPE instructions in the
> application, nothing bad happens!
>
> I am polling the MSR - and it seems the SPE is turned OFF?
You are polling MSR in your application?
Anyway, this is expected. We do lazy restore of these registers after a
context switch. So the SPE bit in the MSR may not be set if no SPE
instructions have run since the last context switch.
> What have I done wrong and/or has there been fixes in later kernels that
> I should be aware of that might help this issue?
I'm not clear what the problem is. You've just said "problems happen"
when you include SPE instructions.
Are you getting a SIGILL or some other signal? Is your program
terminating. Can you get a GDB back-trace or dump of which instruction
is causing the "problem".
Mikey
next prev parent reply other threads:[~2009-05-05 4:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 22:25 MSR_SPE - being turned off Morrison, Tom
2009-05-05 4:17 ` Michael Neuling [this message]
2009-05-05 11:07 ` Kumar Gala
2009-05-05 12:56 ` Morrison, Tom
2009-05-05 21:18 ` Kumar Gala
2009-05-06 0:07 ` Morrison, Tom
2009-05-06 0:01 ` Michael Neuling
2009-05-06 0:42 ` Morrison, Tom
2009-05-06 4:23 ` Kumar Gala
2009-05-06 8:31 ` Morrison, Tom
2009-05-06 12:31 ` Kumar Gala
2009-05-06 12:42 ` Morrison, Tom
2009-05-06 12:44 ` Kumar Gala
2009-05-06 19:33 ` Morrison, Tom
2009-05-06 20:15 ` Morrison, Tom
2009-05-06 21:23 ` Kumar Gala
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=23583.1241497062@neuling.org \
--to=mikey@neuling.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tmorrison@empirix.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 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).