From: "Gérard Guével" <gguevel@interfaceconcept.com>
To: "'Andy Fleming'" <afleming@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: How to use SPE on MPC8541
Date: Tue, 27 Sep 2005 19:36:53 +0200 [thread overview]
Message-ID: <000a01c5c38a$0f77cda0$5201a8c0@GEG2400> (raw)
In-Reply-To: <5D83ECE9-90F7-4BE2-B173-C20CB868E9F6@freescale.com>
> You say the application runs, right? So what made you check the SPE
> bit state? The kernel keeps SPE disabled by default so it doesn't
> have to save the upper 32 bits of the registers every context
> switch. When a process uses SPE for the first time, an exception is
> triggered, the kernel enables SPE for that process, and then that
> process should be able to use SPE every time it gets cpu time.
>
> How are you determining that the SPE bit is not set? Is your
> application not executing the SPE instructions?
>
> Andy
Yes the application runs. I wrote a mini driver with an ioctl which
performs a mfmsr() call and returns the value to the user application.
I called this ioctl at several times before and after executing SPE code.
I already tried to manually force the SPE bit with another ioctl which
performs a enable_kernel_spe() call. The bit SPE is right set at this time
but disappears later.
I don't know if using ioctls is a right way to check the bit.
Any idea ?
Thanks
Gérard
next prev parent reply other threads:[~2005-09-27 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 17:46 Linux Kernel Issue: MPC8540 Errata (CPU29) Chiradeep Vittal
2005-04-27 18:36 ` Kumar Gala
2005-09-27 15:30 ` How to use SPE on MPC8541 Gérard Guével
2005-09-27 15:56 ` Andy Fleming
2005-09-27 17:36 ` Gérard Guével [this message]
2005-09-27 18:50 ` Andy Fleming
2005-09-28 8:02 ` Gérard Guével
2005-09-28 15:32 ` Andy Fleming
2005-09-29 13:23 ` Gérard Guével
-- strict thread matches above, loose matches on Subject: below --
2005-09-28 8:12 Fillod Stephane
2005-09-28 15:34 ` Andy Fleming
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='000a01c5c38a$0f77cda0$5201a8c0@GEG2400' \
--to=gguevel@interfaceconcept.com \
--cc=afleming@freescale.com \
--cc=linuxppc-embedded@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).