All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: "DRI mailing list" <dri-devel@lists.freedesktop.org>,
	"Linaro MM SIG" <linaro-mm-sig@lists.linaro.org>,
	"Jason Ekstrand" <jason@jlekstrand.net>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Dave Airlie" <airlied@redhat.com>,
	"Christian König" <christian.koenig@amd.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH 0/4] dma-buf: Silence dma_fence __rcu sparse warnings
Date: Thu, 9 Nov 2017 21:33:20 +0200	[thread overview]
Message-ID: <20171109193320.GC10981@intel.com> (raw)
In-Reply-To: <CAO_48GHqiC39RZ5iby4h6mT3X5=5REn+nO2XEzqoN3tx3uVpCQ@mail.gmail.com>

On Tue, Nov 07, 2017 at 01:37:10PM +0530, Sumit Semwal wrote:
> Hi Ville,
> 
> On 3 November 2017 at 13:18, Christian König <christian.koenig@amd.com> wrote:
> > Patch #4 is Reviewed-by: Christian König <christian.koenig@amd.com>.
> >
> > The rest is Acked-by: Christian König <christian.koenig@amd.com>.
> >
> > Regards,
> > Christian.
> >
> >
> > Am 02.11.2017 um 21:03 schrieb Ville Syrjala:
> >>
> >> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >>
> >> When building drm+i915 I get around 150 lines of sparse noise from
> >> dma_fence __rcu warnings. This series eliminates all of that.
> >>
> >> The first two patches were already posted by Chris, but there wasn't
> >> any real reaction, so I figured I'd repost with a wider Cc list.
> >>
> >> As for the other two patches, I'm no expert on dma_fence and I didn't
> >> spend a lot of time looking at it so I can't be sure I annotated all
> >> the accesses correctly. But I figured someone will scream at me if
> >> I got it wrong ;)
> >>
> >> Cc: Dave Airlie <airlied@redhat.com>
> >> Cc: Jason Ekstrand <jason@jlekstrand.net>
> >> Cc: linaro-mm-sig@lists.linaro.org
> >> Cc: linux-media@vger.kernel.org
> >> Cc: Alex Deucher <alexander.deucher@amd.com>
> >> Cc: Christian König <christian.koenig@amd.com>
> >> Cc: Sumit Semwal <sumit.semwal@linaro.org>
> >> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> >>
> >> Chris Wilson (2):
> >>    drm/syncobj: Mark up the fence as an RCU protected pointer
> >>    dma-buf/fence: Sparse wants __rcu on the object itself
> >>
> >> Ville Syrjälä (2):
> >>    drm/syncobj: Use proper methods for accessing rcu protected pointers
> >>    dma-buf: Use rcu_assign_pointer() to set rcu protected pointers
> 
> For patches 2 (with Daniel's minor comment) and 4, please feel free to add my
> Acked-by: Sumit Semwal <sumit.semwal@linaro.org.

Thanks everyone. Series pushed to drm-misc-next.

> 
> >>
> >>   drivers/dma-buf/reservation.c |  2 +-
> >>   drivers/gpu/drm/drm_syncobj.c | 11 +++++++----
> >>   include/drm/drm_syncobj.h     |  2 +-
> >>   include/linux/dma-fence.h     |  2 +-
> >>   4 files changed, 10 insertions(+), 7 deletions(-)
> >>
> >
> 
> Best,
> Sumit.

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: "Christian König" <christian.koenig@amd.com>,
	"DRI mailing list" <dri-devel@lists.freedesktop.org>,
	"Dave Airlie" <airlied@redhat.com>,
	"Jason Ekstrand" <jason@jlekstrand.net>,
	"Linaro MM SIG" <linaro-mm-sig@lists.linaro.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Chris Wilson" <chris@chris-wilson.co.uk>
Subject: Re: [PATCH 0/4] dma-buf: Silence dma_fence __rcu sparse warnings
Date: Thu, 9 Nov 2017 21:33:20 +0200	[thread overview]
Message-ID: <20171109193320.GC10981@intel.com> (raw)
In-Reply-To: <CAO_48GHqiC39RZ5iby4h6mT3X5=5REn+nO2XEzqoN3tx3uVpCQ@mail.gmail.com>

On Tue, Nov 07, 2017 at 01:37:10PM +0530, Sumit Semwal wrote:
> Hi Ville,
> 
> On 3 November 2017 at 13:18, Christian König <christian.koenig@amd.com> wrote:
> > Patch #4 is Reviewed-by: Christian König <christian.koenig@amd.com>.
> >
> > The rest is Acked-by: Christian König <christian.koenig@amd.com>.
> >
> > Regards,
> > Christian.
> >
> >
> > Am 02.11.2017 um 21:03 schrieb Ville Syrjala:
> >>
> >> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >>
> >> When building drm+i915 I get around 150 lines of sparse noise from
> >> dma_fence __rcu warnings. This series eliminates all of that.
> >>
> >> The first two patches were already posted by Chris, but there wasn't
> >> any real reaction, so I figured I'd repost with a wider Cc list.
> >>
> >> As for the other two patches, I'm no expert on dma_fence and I didn't
> >> spend a lot of time looking at it so I can't be sure I annotated all
> >> the accesses correctly. But I figured someone will scream at me if
> >> I got it wrong ;)
> >>
> >> Cc: Dave Airlie <airlied@redhat.com>
> >> Cc: Jason Ekstrand <jason@jlekstrand.net>
> >> Cc: linaro-mm-sig@lists.linaro.org
> >> Cc: linux-media@vger.kernel.org
> >> Cc: Alex Deucher <alexander.deucher@amd.com>
> >> Cc: Christian König <christian.koenig@amd.com>
> >> Cc: Sumit Semwal <sumit.semwal@linaro.org>
> >> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> >>
> >> Chris Wilson (2):
> >>    drm/syncobj: Mark up the fence as an RCU protected pointer
> >>    dma-buf/fence: Sparse wants __rcu on the object itself
> >>
> >> Ville Syrjälä (2):
> >>    drm/syncobj: Use proper methods for accessing rcu protected pointers
> >>    dma-buf: Use rcu_assign_pointer() to set rcu protected pointers
> 
> For patches 2 (with Daniel's minor comment) and 4, please feel free to add my
> Acked-by: Sumit Semwal <sumit.semwal@linaro.org.

Thanks everyone. Series pushed to drm-misc-next.

> 
> >>
> >>   drivers/dma-buf/reservation.c |  2 +-
> >>   drivers/gpu/drm/drm_syncobj.c | 11 +++++++----
> >>   include/drm/drm_syncobj.h     |  2 +-
> >>   include/linux/dma-fence.h     |  2 +-
> >>   4 files changed, 10 insertions(+), 7 deletions(-)
> >>
> >
> 
> Best,
> Sumit.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2017-11-09 19:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02 20:03 [PATCH 0/4] dma-buf: Silence dma_fence __rcu sparse warnings Ville Syrjala
2017-11-02 20:03 ` Ville Syrjala
2017-11-02 20:03 ` [PATCH 1/4] drm/syncobj: Mark up the fence as an RCU protected pointer Ville Syrjala
2017-11-02 20:03   ` Ville Syrjala
2017-11-02 20:03 ` [PATCH 2/4] dma-buf/fence: Sparse wants __rcu on the object itself Ville Syrjala
2017-11-06  8:45   ` Daniel Vetter
2017-11-02 20:03 ` [PATCH 3/4] drm/syncobj: Use proper methods for accessing rcu protected pointers Ville Syrjala
2017-11-02 20:03   ` Ville Syrjala
2017-11-02 20:03 ` [PATCH 4/4] dma-buf: Use rcu_assign_pointer() to set " Ville Syrjala
2017-11-02 20:03   ` Ville Syrjala
2017-11-03  7:48 ` [PATCH 0/4] dma-buf: Silence dma_fence __rcu sparse warnings Christian König
2017-11-07  8:07   ` Sumit Semwal
2017-11-09 19:33     ` Ville Syrjälä [this message]
2017-11-09 19:33       ` Ville Syrjälä

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=20171109193320.GC10981@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=airlied@redhat.com \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jason@jlekstrand.net \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sumit.semwal@linaro.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 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.