All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Michel Thierry <michel.thierry@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/guc: Fix doorbell id selection
Date: Tue, 30 May 2017 17:19:26 -0700	[thread overview]
Message-ID: <791e4b94-0f4d-e81b-a032-cfea0e2a1d53@intel.com> (raw)
In-Reply-To: <20170531000546.30762-1-michel.thierry@intel.com>



On 30/05/17 17:05, Michel Thierry wrote:
> We are passing parameters in the wrong order to find next zero bit, and
> when it doesn't find anything it returns size (offset in the code), which
> is always zero.
>
> For reference the function is defined as:
> find_next_bit( *addr, size, offset )
>
> The incorrect parameter order was added by commit abddffdf3620e
> ("drm/i915/guc: Sanitize GuC client initialization"). Luckily, currently
> we only use a single guc client and a single doorbell, which happens to be
> zero; therefore it isn't necessary to backport this fix (which would be for
> v4.12).
>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Oscar Mateo <oscar.mateo@intel.com>
> Signed-off-by: Michel Thierry <michel.thierry@intel.com>
> ---

Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>

Thanks,
Daniele

>  drivers/gpu/drm/i915/i915_guc_submission.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_guc_submission.c b/drivers/gpu/drm/i915/i915_guc_submission.c
> index fb936bb5cb93..ec391ef981aa 100644
> --- a/drivers/gpu/drm/i915/i915_guc_submission.c
> +++ b/drivers/gpu/drm/i915/i915_guc_submission.c
> @@ -105,7 +105,7 @@ static int __reserve_doorbell(struct i915_guc_client *client)
>  		end += offset;
>  	}
>
> -	id = find_next_zero_bit(client->guc->doorbell_bitmap, offset, end);
> +	id = find_next_zero_bit(client->guc->doorbell_bitmap, end, offset);
>  	if (id == end)
>  		return -ENOSPC;
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-05-31  0:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31  0:05 [PATCH] drm/i915/guc: Fix doorbell id selection Michel Thierry
2017-05-31  0:19 ` Daniele Ceraolo Spurio [this message]
2017-05-31  7:37   ` Joonas Lahtinen
2017-05-31  0:21 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-05-31  7:37   ` Joonas Lahtinen

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=791e4b94-0f4d-e81b-a032-cfea0e2a1d53@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michel.thierry@intel.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 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.