From: Michael Ellerman <michael@ellerman.id.au>
To: Kevin Diggs <kevdig@hypersurf.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: to schedule() or not to schedule() ?
Date: Wed, 06 Aug 2008 09:00:56 +1000 [thread overview]
Message-ID: <1217977256.7593.2.camel@localhost> (raw)
In-Reply-To: <4898A96B.40502@hypersurf.com>
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
On Tue, 2008-08-05 at 12:26 -0700, Kevin Diggs wrote:
> Chris Friesen wrote:
> > Kevin Diggs wrote:
> >> I have the following near the top of my cpufreq driver target
> >> routine:
> >>
> >> while(test_and_set_bit(cf750gxmCfgChangeBit,&cf750gxvStateBits)) {
> >> /*
> >> * Someone mucking with our cfg? (I hope it is ok to call
> >> * schedule() here! - truth is I have no idea what I am doing
> >> * ... my reasoning is I want to yeild the cpu so whoever is
> >> * mucking around can finish)
> >> */
> >> schedule();
> >> }
> >>
> >> This is to prevent bad things from happening if someone is trying to
> >> change a parameter for the driver via sysfs while the target routine
> >> is running. Fortunately, because I had a bug where this bit was not
> >> getting cleared on one of the paths through the target routine ... I
> >> now know it is not safe to call schedule (it got stuck in there -
> >> knocked out my adb keyboard! - (I think target is called from a timer
> >> that the governor sets up ... interrupt context?)).
> >
> >
> > Is the issue that someone may be in the middle of a multi-stage
> > procedure, and you've woken up partway through?
> >
> > If so, what about simply rescheduling the timer for some short time in
> > the future and aborting the current call?
> Chris,
>
> Thanks for taking the time to reply. The parameter in question modifies
> the frequency table. It is used several times in the target routine.
> I've addressed the issue by making a local copy of the frequency table
> upon entry to the target routine and use that while there. I don't care
> who wins the race.
How are you copying the table? Is it an atomic copy? Otherwise you could
just end up copying the table while it's being updated, and you get a
copy of the partially updated table.
Don't you just need a spinlock?
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-08-05 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 18:33 to schedule() or not to schedule() ? Kevin Diggs
2008-08-05 18:37 ` Chris Friesen
2008-08-05 19:26 ` Kevin Diggs
2008-08-05 23:00 ` Michael Ellerman [this message]
2008-08-06 1:59 ` Kevin Diggs
2008-08-06 21:12 ` Arnd Bergmann
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=1217977256.7593.2.camel@localhost \
--to=michael@ellerman.id.au \
--cc=kevdig@hypersurf.com \
--cc=linuxppc-dev@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).