From: jmerkey@wolfmountaingroup.com
To: "Stefan Richter" <stefanr@s5r6.in-berlin.de>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>,
jmerkey@wolfmountaingroup.com, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] mdb-2.6.27-rc2-ia32-08-07-08.patch
Date: Sat, 9 Aug 2008 08:44:01 -0600 (MDT) [thread overview]
Message-ID: <44066.166.70.238.43.1218293041.squirrel@webmail.wolfmountaingroup.com> (raw)
In-Reply-To: <489D4F73.5030109@s5r6.in-berlin.de>
> Jeremy Fitzhardinge wrote:
>> Stefan Richter wrote:
>>> jmerkey@wolfmountaingroup.com wrote:
>>>> ftp://ftp.wolfmountaingroup.org/pub/mdb/mdb-2.6.27-rc2-ia32-08-07-08.patch
> [...]
>>> The accessors rspin_lock() and rspin_try_lock() peek into spinlock_t
>>> and
>>> may therefore not be fully portable. Also, they and rspin_unlock()
>>> don't look SMP safe:
>>>
>>>
>>>> +//
>>>> +// returns 0 - atomic lock occurred, processor assigned
>>>> +// 1 - recusive count increased
>>>> +//
>>>> +
>>>> +unsigned long rspin_lock(volatile rlock_t *rlock)
>>>> +{
>>>> +#if defined(CONFIG_SMP)
>>>> + register unsigned long proc = get_processor_id();
>>>> + register unsigned long retCode;
>>>> +
>>>> + if (rlock->lock.raw_lock.slock && rlock->processor == proc)
>>>>
>>
>> Ticket locks will almost always have a non-zero slock. It doesn't
>> indicate anything about the locked/unlocked state. But this looks like
>> it's effectively doing a trylock:
>>
>> if (!spin_trylock(rlock) && rlock->processor == proc) {
>> rlock->count++;
>> ...
>> } else {
>> rlock->processor = proc;
>> ...
>> }
>
> Right. This implemention also looks free of race conditions, provided
> that
>
> - rspin_lock, rspin_try_lock, and rspin_unlock are only called in
> contexts with disabled preemption and disabled local interrupts,
>
> - rspin_unlock() rewrites rlock->processor to "no CPU" before
> it drops the lock. (The implementation in
> mdb-2.6.27-rc2-ia32-08-07-08.patch does so.)
>
> BTW, the rspin_try_lock() in that patch wrong: It always returns 0
> instead of having three branches of execution which return 0/1/-1.
.... On linux it does -- on another OS it does something quite different.
I changed that case last night when I added spin)is_locked calls. Is
there
to do a "debugger bust spinlocks" if the system ever hangs in the
debugger. probably should code it different.
Jeff
:-)
Jeff
> --
> Stefan Richter
> -=====-==--- =--- -=--=
> http://arcgraph.de/sr/
>
next prev parent reply other threads:[~2008-08-09 15:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 14:29 jmerkey
2008-08-07 15:49 ` Stefan Richter
2008-08-07 15:59 ` Stefan Richter
2008-08-07 15:56 ` jmerkey
2008-08-07 16:46 ` Stefan Richter
2008-08-07 16:33 ` jmerkey
2008-08-07 17:19 ` Stefan Richter
2008-08-07 17:33 ` Stefan Richter
2008-08-07 17:52 ` jmerkey
2008-08-07 17:52 ` jmerkey
2008-08-07 16:04 ` jmerkey
2008-08-09 5:07 ` Jeremy Fitzhardinge
2008-08-09 8:04 ` Stefan Richter
2008-08-09 14:44 ` jmerkey [this message]
2008-08-08 2:18 ` Parag Warudkar
2008-08-08 4:33 Parag Warudkar
2008-08-08 13:11 ` jmerkey
[not found] ` <37357.166.70.238.45.1218201115.squirrel@webmail.wolfmountaingroup.com >
2008-08-08 13:23 ` jmerkey
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=44066.166.70.238.43.1218293041.squirrel@webmail.wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®