From: Nish Aravamudan <nish.aravamudan@gmail.com>
To: Pavel Machek <pavel@suse.cz>
Cc: rpurdie@rpsys.net, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>,
rmk@arm.linux.org.uk, vojtech@suse.cz
Subject: Re: [patch,rfc] Support for touchscreen on sharp zaurus sl-5500
Date: Thu, 21 Jul 2005 22:02:46 -0700 [thread overview]
Message-ID: <29495f1d050721220276c8733c@mail.gmail.com> (raw)
In-Reply-To: <20050722012814.GB6758@atrey.karlin.mff.cuni.cz>
On 7/21/05, Pavel Machek <pavel@suse.cz> wrote:
> Hi!
>
> > > + set_task_state(tsk, TASK_UNINTERRUPTIBLE);
> > > + schedule_timeout(HZ / 100);
> > > + if (signal_pending(tsk))
> > > + break;
> >
> > You specifically allow SIGKILL, but then sleep uninterruptibly? And
> > then you check if signal_pending() :) I think you may want
> > TASK_INTERRUPTIBLE? Or, go one better and use msleep_interruptible(),
> > as I don't see any wait-queues in the immediate area of this code...
>
> Okay, I think this should be uninterruptible. The signal can be
> delivered during next interruptible sleep. Fixes.
Good point. But the signal_pending() check after that interruptible
sleep (which deterministically comes after this one) takes care of the
break, doesn't it? I guess you can (maybe already have done so...) get
rid of the signal_pending() check after the uninterruptible sleep. And
then go ahead and make this an msleep(10) call and the other one (in
the same function) an msleep_interruptible() call ;)
Thanks,
Nish
prev parent reply other threads:[~2005-07-22 5:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 5:24 [patch,rfc] Support for touchscreen on sharp zaurus sl-5500 Pavel Machek
2005-07-21 5:50 ` Dmitry Torokhov
2005-07-21 15:40 ` Pavel Machek
2005-07-22 0:24 ` Nish Aravamudan
2005-07-22 1:28 ` Pavel Machek
2005-07-22 5:02 ` Nish Aravamudan [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=29495f1d050721220276c8733c@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rmk@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
--cc=vojtech@suse.cz \
/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