All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris.p.wilson@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Remove unwanted rcu_read_lock/unlock
Date: Wed, 06 Nov 2019 00:42:03 +0000	[thread overview]
Message-ID: <157300092336.21573.10540959417252452757@skylake-alporthouse-com> (raw)
In-Reply-To: <20191106000205.22480-2-niranjana.vishwanathapura@intel.com>

Quoting Niranjana Vishwanathapura (2019-11-06 00:02:03)
> We don't need rcu read side critical section to call pid_nr(),
> remove it.
> 
> Cc: Chris P Wilson <chris.p.wilson@intel.com>
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_gpu_error.c | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index e8b67f5e521d..1f2f266f26af 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -1230,10 +1230,7 @@ static void record_request(const struct i915_request *request,
>         erq->start = i915_ggtt_offset(request->ring->vma);
>         erq->head = request->head;
>         erq->tail = request->tail;
> -
> -       rcu_read_lock();
>         erq->pid = ctx->pid ? pid_nr(ctx->pid) : 0;
> -       rcu_read_unlock();

Ok, that was just cut'n'paste from pid_task()
Reviewed-by: Chris Wilson <chris.p.wilson@intel.com>
-Chris
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris.p.wilson@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915: Remove unwanted rcu_read_lock/unlock
Date: Wed, 06 Nov 2019 00:42:03 +0000	[thread overview]
Message-ID: <157300092336.21573.10540959417252452757@skylake-alporthouse-com> (raw)
Message-ID: <20191106004203.uDc9ZM5-fbgLs7R1o8zY4yp5LBllBEc8UxIYfLp778Q@z> (raw)
In-Reply-To: <20191106000205.22480-2-niranjana.vishwanathapura@intel.com>

Quoting Niranjana Vishwanathapura (2019-11-06 00:02:03)
> We don't need rcu read side critical section to call pid_nr(),
> remove it.
> 
> Cc: Chris P Wilson <chris.p.wilson@intel.com>
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_gpu_error.c | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index e8b67f5e521d..1f2f266f26af 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -1230,10 +1230,7 @@ static void record_request(const struct i915_request *request,
>         erq->start = i915_ggtt_offset(request->ring->vma);
>         erq->head = request->head;
>         erq->tail = request->tail;
> -
> -       rcu_read_lock();
>         erq->pid = ctx->pid ? pid_nr(ctx->pid) : 0;
> -       rcu_read_unlock();

Ok, that was just cut'n'paste from pid_task()
Reviewed-by: Chris Wilson <chris.p.wilson@intel.com>
-Chris
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-11-06  0:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191106000205.22480-1-niranjana.vishwanathapura@intel.com>
     [not found] ` <20191106000205.22480-4-niranjana.vishwanathapura@intel.com>
2019-11-06  0:36   ` [PATCH 3/3] drm/i915: Use rcu_dereference for rcu protected pointer Chris Wilson
2019-11-06  0:36     ` [Intel-gfx] " Chris Wilson
2019-11-06  2:16     ` Niranjan Vishwanathapura
2019-11-06  2:16       ` [Intel-gfx] " Niranjan Vishwanathapura
2019-11-06  8:52       ` Chris Wilson
2019-11-06  8:52         ` [Intel-gfx] " Chris Wilson
2019-11-07  5:05         ` Niranjan Vishwanathapura
2019-11-07  5:05           ` [Intel-gfx] " Niranjan Vishwanathapura
2019-11-07  9:49           ` Chris Wilson
2019-11-07  9:49             ` [Intel-gfx] " Chris Wilson
     [not found] ` <20191106000205.22480-3-niranjana.vishwanathapura@intel.com>
2019-11-06  0:37   ` [PATCH 2/3] drm/i915: Check for ips_mchdev being NULL Chris Wilson
2019-11-06  0:37     ` [Intel-gfx] " Chris Wilson
2019-11-06  2:14     ` Niranjan Vishwanathapura
2019-11-06  2:14       ` [Intel-gfx] " Niranjan Vishwanathapura
2019-11-06  8:40       ` Chris Wilson
2019-11-06  8:40         ` [Intel-gfx] " Chris Wilson
     [not found] ` <20191106000205.22480-2-niranjana.vishwanathapura@intel.com>
2019-11-06  0:42   ` Chris Wilson [this message]
2019-11-06  0:42     ` [Intel-gfx] [PATCH 1/3] drm/i915: Remove unwanted rcu_read_lock/unlock Chris Wilson

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=157300092336.21573.10540959417252452757@skylake-alporthouse-com \
    --to=chris.p.wilson@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=niranjana.vishwanathapura@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.