From: Boris Brezillon <boris.brezillon@collabora.com>
To: Steven Price <steven.price@arm.com>
Cc: dri-devel@lists.freedesktop.org, Rob Herring <robh+dt@kernel.org>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
Subject: Re: [PATCH v2] drm/panfrost: Document base field location constraint in panfrost_gem_object
Date: Fri, 29 Nov 2019 15:19:36 +0100 [thread overview]
Message-ID: <20191129151936.5fb18d2e@collabora.com> (raw)
In-Reply-To: <b603bc00-832c-ae0d-8dfa-57a0b791d6f9@arm.com>
On Fri, 29 Nov 2019 14:13:33 +0000
Steven Price <steven.price@arm.com> wrote:
> On 29/11/2019 13:56, Boris Brezillon wrote:
> > I've spent hours chasing a memory corruption that was caused by
> > insertion of an extra field field before ->base. Let's document the
> > fact that base has to be the first field in panfrost_gem_object.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
>
> This seems to be a limitation imposed by the gem_create_object()
> callback - e.g. it's assumed that kfree() can be directly called on the
> result. Useful to have the documentation though.
Oh, you're right, I didn't catch that one.
>
> Reviewed-by: Steven Price <steven.price@arm.com>
>
> Steve
>
> > ---
> > Changes in v2:
> > * Use the proper prefix in the subject line
> > ---
> > drivers/gpu/drm/panfrost/panfrost_gem.h | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/panfrost/panfrost_gem.h b/drivers/gpu/drm/panfrost/panfrost_gem.h
> > index b3517ff9630c..d480261fc177 100644
> > --- a/drivers/gpu/drm/panfrost/panfrost_gem.h
> > +++ b/drivers/gpu/drm/panfrost/panfrost_gem.h
> > @@ -10,6 +10,10 @@
> > struct panfrost_mmu;
> >
> > struct panfrost_gem_object {
> > + /*
> > + * Must be the first element because we're using some of the
> > + * drm_gem_shmem helpers.
> > + */
> > struct drm_gem_shmem_object base;
> > struct sg_table *sgts;
> >
> >
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-11-29 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 13:56 [PATCH v2] drm/panfrost: Document base field location constraint in panfrost_gem_object Boris Brezillon
2019-11-29 14:13 ` Steven Price
2019-11-29 14:19 ` Boris Brezillon [this message]
2019-11-29 18:40 ` Daniel Vetter
2019-11-29 19:24 ` Boris Brezillon
2019-11-29 19:43 ` Ville Syrjälä
2019-11-29 22:23 ` Boris Brezillon
2019-11-29 14:16 ` Alyssa Rosenzweig
2019-11-29 14:28 ` 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=20191129151936.5fb18d2e@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=robh+dt@kernel.org \
--cc=steven.price@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox