All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: [Kernel-janitors] Re: [PATCH 2.6.9-rc2 11/33] char/i830_irq:
Date: Fri, 17 Sep 2004 16:10:48 +0000	[thread overview]
Message-ID: <20040917161048.GA1712@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409161253580.14212@server.home>

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

On Fri, Sep 17, 2004 at 12:38:40AM -0400, Jon Smirl wrote:
> schedule_timeout() is also used in DRM_WAIT_ON() in drm_os_linux.h 
> Does it need to be adjusted too?
> 
> #define DRM_WAIT_ON( ret, queue, timeout, condition )		\
> do {								\
> 	DECLARE_WAITQUEUE(entry, current);			\
> 	unsigned long end = jiffies + (timeout);		\
> 	add_wait_queue(&(queue), &entry);			\
> 								\
> 	for (;;) {						\
> 		__set_current_state(TASK_INTERRUPTIBLE);	\
> 		if (condition)					\
> 			break;					\
> 		if (time_after_eq(jiffies, end)) {		\
> 			ret = -EBUSY;				\
> 			break;					\
> 		}						\
> 		schedule_timeout((HZ/100 > 1) ? HZ/100 : 1);	\
> 		if (signal_pending(current)) {			\
> 			ret = -EINTR;				\
> 			break;					\
> 		}						\
> 	}							\
> 	__set_current_state(TASK_RUNNING);				\
> 	remove_wait_queue(&(queue), &entry);			\
> } while (0)

I did notice this other occurrence, but since the timeout is not
necessarily a long one (measurable in msecs), i.e. in system's where
HZ < 100, I didn't want to make the code more complicated than it is.

But, if some of the DRM people who are more familiar with the hardware
are ok with there always being a 10 ms delay (which it would be for all
system's with HZ > 100 anyways), I could make that change.

Thanks,
Nish

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2004-09-17 16:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 19:54 [Kernel-janitors] Re: [PATCH 2.6.9-rc2 19/33] char/pcxx: replace Christoph Lameter
2004-09-17  4:38 ` [Kernel-janitors] Re: [PATCH 2.6.9-rc2 11/33] char/i830_irq: Jon Smirl
2004-09-17 16:10 ` Nishanth Aravamudan [this message]
2004-09-18 16:46 ` Jon Smirl
2004-09-19  9:39 ` Dave Airlie
2004-09-20 22:11 ` [Kernel-janitors] Re: [PATCH 2.6.9-rc2 17/17] media/zr36120: Nishanth Aravamudan
2004-09-21 21:58 ` [Kernel-janitors] Re: [PATCH 2.6.9-rc2 1/40] net/3c505: replace Phil Blundell
2004-09-21 23:49 ` [Kernel-janitors] Re: [PATCH 2.6.9-rc2 1/2] i2c/i2c-algo-ite: Greg KH
2004-09-27 18:21 ` [Kernel-janitors] Re: [PATCH 2.6.9-rc2 1/16] scsi/53c700: replace James Bottomley
2004-09-27 18:39 ` Nishanth Aravamudan
2004-09-27 19:35 ` [Kernel-janitors] Re: [PATCH 2.6.9-rc2 15/16] scsi/st: replace Kai Makisara
2004-09-27 21:15 ` [Kernel-janitors] Re: [PATCH 2.6.9-rc2 1/6] serial/68328serial: Nishanth Aravamudan
2004-09-27 23:07 ` [Kernel-janitors] Re: [PATCH 2.6.9-rc2 1/4] video/pxafb: replace Nishanth Aravamudan
2004-09-28  1:00 ` [Kernel-janitors] Re: [PATCH 2.6.9-rc2 1/6] serial/68328serial: David McCullough
2004-09-28  3:19 ` [Kernel-janitors] Re: [PATCH 2.6.9-rc2 1/4] w1/dscore: replace Evgeniy Polyakov
2004-09-28  3:25 ` Evgeniy Polyakov
2004-09-29 17:41 ` [Kernel-janitors] Re: [PATCH 2.6.9-rc2 1/4] pci Greg KH

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=20040917161048.GA1712@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=kernel-janitors@vger.kernel.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 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.