From: Chris Wilson <chris@chris-wilson.co.uk>
To: Niranjan Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: Use rcu_dereference for rcu protected pointer
Date: Thu, 07 Nov 2019 09:49:28 +0000 [thread overview]
Message-ID: <157312016887.26738.6871601455648596824@skylake-alporthouse-com> (raw)
In-Reply-To: <20191107050525.GG19940@nvishwa1-DESK.sc.intel.com>
Quoting Niranjan Vishwanathapura (2019-11-07 05:05:26)
> On Wed, Nov 06, 2019 at 08:52:58AM +0000, Chris Wilson wrote:
> >Sure, for correctness see clone_vm().
>
> Ok, I can put a common helper function like vm_get_rcu_safe(ctx).
https://patchwork.freedesktop.org/patch/339110/?series=69044&rev=1
-Chris
_______________________________________________
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@chris-wilson.co.uk>
To: Niranjan Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 3/3] drm/i915: Use rcu_dereference for rcu protected pointer
Date: Thu, 07 Nov 2019 09:49:28 +0000 [thread overview]
Message-ID: <157312016887.26738.6871601455648596824@skylake-alporthouse-com> (raw)
Message-ID: <20191107094928.u7lvFUCFLmcJAfwMWMchu0fqNJ6K-TOwCXx_UNdN1Tc@z> (raw)
In-Reply-To: <20191107050525.GG19940@nvishwa1-DESK.sc.intel.com>
Quoting Niranjan Vishwanathapura (2019-11-07 05:05:26)
> On Wed, Nov 06, 2019 at 08:52:58AM +0000, Chris Wilson wrote:
> >Sure, for correctness see clone_vm().
>
> Ok, I can put a common helper function like vm_get_rcu_safe(ctx).
https://patchwork.freedesktop.org/patch/339110/?series=69044&rev=1
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-07 9:49 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 [this message]
2019-11-07 9:49 ` 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 ` [PATCH 1/3] drm/i915: Remove unwanted rcu_read_lock/unlock Chris Wilson
2019-11-06 0:42 ` [Intel-gfx] " 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=157312016887.26738.6871601455648596824@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--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.