From: Pavel Machek <pavel@suse.cz>
To: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: Robert Love <rml@novell.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] IBM HDAPS accelerometer driver.
Date: Mon, 29 Aug 2005 10:35:52 +0200 [thread overview]
Message-ID: <20050829083552.GD28077@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.62.0508282109040.1489@artax.karlin.mff.cuni.cz>
Hi!
> >>I think he doesn't need to export it at all and he should write code to
> >>park and disable hard disk instead.
> >>(in userspace it's unsolvable --- i.e. you can't enable hard disk when
> >>detected stable condition if the daemon is swapped out on that hard disk)
> >
> >man mlockall() :-).
>
> You also must not use any syscall that allocates even temporary memory in
> kernel (select, poll, many others ...) or that waits on semaphore that
> might be held while allocating memory (i.e. audit and rewrite ide ioctl
> path).
Kernel module would have exactly same problem.
> And you need extra flags to protect the daemon from being killed at
> shutdown or blocked at suspend.
Why?
> >Accelerometer is usefull for other stuff besides parking heads, like
> >playing marble madness or what is the name of the game, and even
> >parking heads is way too complex to be put into the kernel.
> >
> >Even if you don't like mlockall(), you can put timeout into
> >disk-freezing interface.
>
> That makes the protection less reliable (you shake the notebook and after
> the timeout drop it).
Idea is that userland app keeps saying "unfreeze 5 seconds in future"
as long as you keep shaking -- essentialy a deadlock prevention.
Pavel
--
if you have sharp zaurus hardware you don't need... you know my address
next prev parent reply other threads:[~2005-08-29 8:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 15:18 [patch] IBM HDAPS accelerometer driver Robert Love
2005-08-26 17:05 ` Bill Nottingham
2005-08-26 17:15 ` Robert Love
2005-08-26 17:33 ` Brian Gerst
2005-08-26 17:33 ` Robert Love
2005-08-26 18:01 ` Arjan van de Ven
2005-08-26 18:03 ` Robert Love
2005-08-26 18:45 ` Dave Jones
2005-08-26 18:52 ` Robert Love
2005-08-26 19:55 ` Alan Cox
2005-08-26 19:29 ` Robert Love
2005-08-26 19:33 ` Jeff Garzik
2005-08-26 19:37 ` Robert Love
2005-08-26 20:21 ` Alan Cox
2005-08-26 22:43 ` Andi Kleen
2005-08-26 20:27 ` Dave Jones
2005-08-26 19:54 ` Alan Cox
2005-08-26 18:18 ` Andrew Morton
2005-08-26 18:30 ` Robert Love
2005-08-26 19:27 ` Dmitry Torokhov
2005-08-26 19:39 ` Robert Love
2005-08-26 19:43 ` Robert Love
2005-08-26 20:09 ` Dmitry Torokhov
2005-08-26 20:12 ` Dmitry Torokhov
2005-08-28 11:00 ` Yani Ioannou
2005-08-27 12:41 ` Pavel Machek
2005-08-28 2:59 ` Mikulas Patocka
2005-08-28 8:09 ` Pavel Machek
2005-08-28 9:21 ` Oliver Neukum
2005-08-28 19:30 ` Mikulas Patocka
2005-08-29 8:35 ` Pavel Machek [this message]
2005-08-29 8:59 ` Oliver Neukum
2005-08-29 9:10 ` Pavel Machek
2005-08-30 17:44 ` Mikulas Patocka
2005-08-31 0:12 ` Yani Ioannou
[not found] <4FOa3-8fm-39@gated-at.bofh.it>
[not found] ` <4GlyV-3Rk-3@gated-at.bofh.it>
[not found] ` <4GqyE-2bk-19@gated-at.bofh.it>
[not found] ` <4GrEp-3E2-21@gated-at.bofh.it>
2005-08-28 16:26 ` Robert Hancock
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=20050829083552.GD28077@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=rml@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox