public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas@shipmail.org>
To: Roel Kluin <roel.kluin@gmail.com>
Cc: airlied@linux.ie, dri-devel@lists.sourceforge.net,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm: count reaches -1, tested 0
Date: Mon, 09 Feb 2009 23:22:31 +0100	[thread overview]
Message-ID: <4990ACA7.2080100@shipmail.org> (raw)
In-Reply-To: <498EEB42.1050509@gmail.com>

Hi!

Roel Kluin wrote:
> With a postfix decrement count will reach -1 rather than 0,
> subsequent tests fail.
>   
This code is about to be abandoned, but if we're going to fix it, 
instead of pushing the problem to then next while loop, what about

while (count && condition)
    count--;

Can you redo the patch based on that?


Thanks,
Thomas

> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> ---
> diff --git a/drivers/gpu/drm/via/via_dma.c b/drivers/gpu/drm/via/via_dma.c
> index 7a339db..600315c 100644
> --- a/drivers/gpu/drm/via/via_dma.c
> +++ b/drivers/gpu/drm/via/via_dma.c
> @@ -481,9 +481,9 @@ static int via_wait_idle(drm_via_private_t * dev_priv)
>  {
>  	int count = 10000000;
>  
> -	while (!(VIA_READ(VIA_REG_STATUS) & VIA_VR_QUEUE_BUSY) && count--);
> +	while (!(VIA_READ(VIA_REG_STATUS) & VIA_VR_QUEUE_BUSY) && --count);
>  
> -	while (count-- && (VIA_READ(VIA_REG_STATUS) &
> +	while (--count && (VIA_READ(VIA_REG_STATUS) &
>  			   (VIA_CMD_RGTR_BUSY | VIA_2D_ENG_BUSY |
>  			    VIA_3D_ENG_BUSY))) ;
>  	return count;
> @@ -705,7 +705,7 @@ static int via_cmdbuf_size(struct drm_device *dev, void *data, struct drm_file *
>  	switch (d_siz->func) {
>  	case VIA_CMDBUF_SPACE:
>  		while (((tmp_size = via_cmdbuf_space(dev_priv)) < d_siz->size)
> -		       && count--) {
> +		       && --count) {
>  			if (!d_siz->wait) {
>  				break;
>  			}
> @@ -717,7 +717,7 @@ static int via_cmdbuf_size(struct drm_device *dev, void *data, struct drm_file *
>  		break;
>  	case VIA_CMDBUF_LAG:
>  		while (((tmp_size = via_cmdbuf_lag(dev_priv)) > d_siz->size)
> -		       && count--) {
> +		       && --count) {
>  			if (!d_siz->wait) {
>  				break;
>  			}
>
>
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and code to
> build responsive, highly engaging applications that combine the power of local
> resources and data with the reach of the web. Download the Adobe AIR SDK and
> Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
> --
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dri-devel
>   




  parent reply	other threads:[~2009-02-09 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08 14:25 [PATCH] drm: count reaches -1, tested 0 Roel Kluin
2009-02-09  2:28 ` Dave Airlie
2009-02-09 22:22 ` Thomas Hellström [this message]
2009-02-10 20:48   ` [PATCH v2] " Roel Kluin

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=4990ACA7.2080100@shipmail.org \
    --to=thomas@shipmail.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roel.kluin@gmail.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