intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Paulo Zanoni <paulo.r.zanoni@intel.com>
To: Dave Gordon <david.s.gordon@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Only expand COND once in wait_for()
Date: Wed, 14 Sep 2016 15:53:32 -0300	[thread overview]
Message-ID: <1473879212.2435.115.camel@intel.com> (raw)
In-Reply-To: <1473855033-26980-1-git-send-email-david.s.gordon@intel.com>

Em Qua, 2016-09-14 às 13:10 +0100, Dave Gordon escreveu:
> Commentary from Chris Wilson's original version:
> 
> > 
> > I was looking at some wait_for() timeouts on a slow system, with
> > lots of
> > debug enabled (KASAN, lockdep, mmio_debug). Thinking that we were
> > mishandling the timeout, I tried to ensure that we loop at least
> > once
> > after first testing COND. However, the double test of COND either
> > side
> > of the timeout check makes that unlikely. But we can do an
> > equivalent
> > loop, that keeps the COND check after testing for timeout (required
> > so
> > that we are not preempted between testing COND and then testing for
> > a
> > timeout) without expanding COND twice.
> > 
> > The advantage of only expanding COND once is a dramatic reduction
> > in
> > code size:
> > 
> >    text	   data	    bss	    dec	    hex
> >    1308733	   5184	   1152	1315069	 141
> > 0fd	before
> >    1305341	   5184	   1152	1311677	 140
> > 3bd	after
> 
> but it turned out that due to a missing iniitialiser, gcc had "gone
> wild trimming undefined code" :( This version acheives a rather more
> modest (but still worthwhile) gain of ~550 bytes.
> 
> Signed-off-by: Dave Gordon <david.s.gordon@intel.com>
> Original-idea-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Zanoni, Paulo R <paulo.r.zanoni@intel.com>

Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>

> ---
>  drivers/gpu/drm/i915/intel_drv.h | 14 +++++++++-----
>  1 file changed, 9 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_drv.h
> b/drivers/gpu/drm/i915/intel_drv.h
> index abe7a4d..8fd16ad 100644
> --- a/drivers/gpu/drm/i915/intel_drv.h
> +++ b/drivers/gpu/drm/i915/intel_drv.h
> @@ -52,11 +52,15 @@
>   */
>  #define _wait_for(COND, US, W) ({ \
>  	unsigned long timeout__ = jiffies + usecs_to_jiffies(US) +
> 1;	\
> -	int ret__ = 0;						
> 	\
> -	while (!(COND)) {						
> \
> -		if (time_after(jiffies, timeout__)) {		
> 	\
> -			if (!(COND))					
> \
> -				ret__ = -ETIMEDOUT;			
> \
> +	int ret__;							
> \
> +	for (;;) {							
> \
> +		bool expired__ = time_after(jiffies, timeout__);	
> \
> +		if (COND) {						
> \
> +			ret__ = 0;					
> \
> +			break;					
> 	\
> +		}							
> \
> +		if (expired__) {					
> \
> +			ret__ = -ETIMEDOUT;				
> \
>  			break;					
> 	\
>  		}							
> \
>  		if ((W) && drm_can_sleep()) {			
> 	\
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-09-14 18:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 19:40 [PATCH] drm/i915: Only expand COND once in wait_for() Chris Wilson
2016-09-13 21:05 ` Zanoni, Paulo R
2016-09-14  5:37 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-09-14  9:22 ` [PATCH] " Chris Wilson
2016-09-14 12:10   ` Dave Gordon
2016-09-14 18:53     ` Paulo Zanoni [this message]
2016-09-15  9:50       ` Chris Wilson
2016-09-14 13:37   ` Zanoni, Paulo R
2016-09-14 12:49 ` ✗ Fi.CI.BAT: failure for drm/i915: Only expand COND once in wait_for() (rev2) Patchwork
2016-09-15  7:20 ` ✓ Fi.CI.BAT: success " Patchwork
2016-09-19  1:40 ` [lkp] [drm/i915] c19d736b05: WARNING: CPU: 0 PID: 236 at drivers/gpu/drm/i915/intel_display.c:1085 intel_disable_pipe+0x157/0x250 [i915] kernel test robot

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=1473879212.2435.115.camel@intel.com \
    --to=paulo.r.zanoni@intel.com \
    --cc=david.s.gordon@intel.com \
    --cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).