From: Darcy Watkins <dwatkins@tranzeo.com>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Strange Badness with RT Spin Lock
Date: Wed, 13 Aug 2008 12:55:22 -0700 [thread overview]
Message-ID: <1218657322.3465.93.camel@localhost> (raw)
In-Reply-To: <1218225371.3465.51.camel@localhost>
I have an update...
First please disregard the follow-up email I sent mentioning memory
barriers. That blew up shortly after I sent out the email.
The problem appears to be resolved when I declare the spinlock variable
using the __cacheline_aligned attribute (that is without the _in_smp
suffix).
Does anyone know of an explanation as to why a spinlock may need to be
cacheline aligned in a uniprocessor system?
Regards,
Darcy
On Fri, 2008-08-08 at 12:56 -0700, Darcy Watkins wrote:
> Hello,
>
> I have a very unusual bug I have been trying to get to the bottom of.
>
> First the background...
>
> AMCC PPC405EP on embedded network device (simpler than a Taihu)
> Kernel 2.6.25.8-rt7 with incremental patches up to 2.6.25.13
> mPCI slot with a WiMax radio card
>
> This is an RT-Preemption kernel.
>
> In my system, in a real time radio (WiMax) driver, I have code that
> makes use of a spinlock to control access to a tree structure...
>
> spinlock_t tree_lock;
>
--
Regards,
Darcy
--------------
Darcy L. Watkins - Senior Software Developer
Tranzeo Wireless Technologies, Inc.
19273 Fraser Way, Pitt Meadows, BC, Canada V3Y 2V4
T:604-460-6002 ext:410
http://www.tranzeo.com
prev parent reply other threads:[~2008-08-13 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 19:56 Strange Badness with RT Spin Lock Darcy Watkins
2008-08-11 15:30 ` Darcy Watkins
2008-08-13 19:55 ` Darcy Watkins [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=1218657322.3465.93.camel@localhost \
--to=dwatkins@tranzeo.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).