From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH] powerpc: Move CPM command handling into the cpm drivers
Date: Tue, 27 Nov 2007 00:22:49 +0300 [thread overview]
Message-ID: <20071127002249.612f4ff6@kernel.crashing.org> (raw)
In-Reply-To: <20071126162446.GA4408@loki.buserror.net>
On Mon, 26 Nov 2007 10:24:46 -0600
Scott Wood wrote:
> On Fri, Nov 23, 2007 at 12:51:21AM +0300, Vitaly Bordug wrote:
> > Even that might be not enough - we may have simultaneous call of
> > this func in non-smp case...
>
> Do you really think that every piece of code that uses spinlocks in
> the kernel is broken on non-SMP?
>
No. I think spinlock is not universal save thing in such cases. See below.
> > I was thinking of some kind of refcount, so one that is going to
> > issue CPM command, must do say pq_cpmp_get() and another driver
> > won't be able to mangle with cpcr while it's not done with previous
> > request.
>
> How on earth are you going to effect mutual exclusion using reference
> counting?
>
perhaps I was not clear enough. That was a rough idea how to handle the whole thing,
not just cpm_cr_cmd. This cpm command is a corner case, but there can be other actions
that may confuse CPM being triggered simultaneously or overlapping. This is part of much bigger
problem, and I was intended to have a look what people think about that.
--
Sincerely, Vitaly
next prev parent reply other threads:[~2007-11-26 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 17:24 [RFC/PATCH] powerpc: Move CPM command handling into the cpm drivers Jochen Friedrich
2007-11-22 18:36 ` Grant Likely
2007-11-22 21:51 ` Vitaly Bordug
2007-11-24 17:53 ` Jochen Friedrich
2007-11-24 21:47 ` Vitaly Bordug
2007-11-26 16:24 ` Scott Wood
2007-11-26 21:22 ` Vitaly Bordug [this message]
2007-11-26 21:41 ` Scott Wood
2007-11-27 8:08 ` Vitaly Bordug
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=20071127002249.612f4ff6@kernel.crashing.org \
--to=vitb@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.