From: Andrew Morton <akpm@osdl.org>
To: domen@coderock.org
Cc: linux-kernel@vger.kernel.org, domen@coderock.org, nacc@us.ibm.com
Subject: Re: [patch 05/14] char/hvsi: use wait_event_timeout()
Date: Sun, 6 Mar 2005 19:32:36 -0800 [thread overview]
Message-ID: <20050306193236.1dd2b3de.akpm@osdl.org> (raw)
In-Reply-To: <20050306223630.55D7C1ED3D@trashy.coderock.org>
domen@coderock.org wrote:
>
> Please consider applying. This is my first wait-queue related patch, so comments
> are very welcome.
>
> Use wait_event_timeout() in place of custom wait-queue code. The
> code is not changed in any way (I don't think), but is cleaned up quite a bit
> (will get expanded to almost identical code).
>
> ...
> diff -puN drivers/char/hvsi.c~wait_event_timeout-drivers_char_hvsi drivers/char/hvsi.c
> --- kj/drivers/char/hvsi.c~wait_event_timeout-drivers_char_hvsi 2005-03-05 16:11:27.000000000 +0100
> +++ kj-domen/drivers/char/hvsi.c 2005-03-05 16:11:27.000000000 +0100
> @@ -44,6 +44,7 @@
> #include <linux/sysrq.h>
> #include <linux/tty.h>
> #include <linux/tty_flip.h>
> +#include <linux/wait.h>
> #include <asm/hvcall.h>
> #include <asm/hvconsole.h>
> #include <asm/prom.h>
> @@ -631,27 +632,10 @@ static int __init poll_for_state(struct
> /* wait for irq handler to change our state */
> static int wait_for_state(struct hvsi_struct *hp, int state)
> {
> - unsigned long end_jiffies = jiffies + HVSI_TIMEOUT;
> - unsigned long timeout;
> int ret = 0;
>
> - DECLARE_WAITQUEUE(myself, current);
> - set_current_state(TASK_INTERRUPTIBLE);
> - add_wait_queue(&hp->stateq, &myself);
> -
> - for (;;) {
> - set_current_state(TASK_INTERRUPTIBLE);
> - if (hp->state == state)
> - break;
> - timeout = end_jiffies - jiffies;
> - if (time_after(jiffies, end_jiffies)) {
> - ret = -EIO;
> - break;
> - }
> - schedule_timeout(timeout);
> - }
> - remove_wait_queue(&hp->stateq, &myself);
> - set_current_state(TASK_RUNNING);
> + if(!wait_event_timeout(hp->stateq, (hp->state == state), jiffies + HVSI_TIMEOUT))
> + ret = -EIO;
wait_event_timeout()'s `timeout' arg is number-of-milliseconds-to-wait,
not an absolute time, yes?
Also, it's conventional to put a space between the `if' and the `('.
It's nice to squeeze the code into an 80-column xterm, too.
next prev parent reply other threads:[~2005-03-07 3:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 22:36 [patch 05/14] char/hvsi: use wait_event_timeout() domen
2005-03-07 3:32 ` Andrew Morton [this message]
2005-03-07 4:56 ` Nish Aravamudan
2005-03-08 0:15 ` [UPDATE PATCH] " Nishanth Aravamudan
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=20050306193236.1dd2b3de.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=domen@coderock.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nacc@us.ibm.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