From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Initialise the obj->rcu head
Date: Fri, 09 Nov 2018 10:49:27 +0000 [thread overview]
Message-ID: <154176056755.30559.2472619344322307125@skylake-alporthouse-com> (raw)
In-Reply-To: <87d0reh77l.fsf@gaia.fi.intel.com>
Quoting Mika Kuoppala (2018-11-09 10:32:30)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
>
> > Make the rcu_head known to the system, in particular for debugobjects.
> > And having declared it for debugobjects, we need to tidy up afterwards.
> >
> > v2: mark the obj->rcu as being destroy when we reuse its location for
> > the freed list.
> >
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108691
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Merged the first as it will close a couple of bugs, care to check over
the second? :)
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-11-09 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 9:21 [PATCH 1/2] drm/i915: Initialise the obj->rcu head Chris Wilson
2018-11-08 9:21 ` [PATCH 2/2] drm/i915: Track rcu_head for our idle worker Chris Wilson
2018-11-09 11:25 ` Mika Kuoppala
2018-11-08 10:01 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: Initialise the obj->rcu head Patchwork
2018-11-09 8:40 ` [PATCH 1/2] " Mika Kuoppala
2018-11-09 9:00 ` Chris Wilson
2018-11-09 9:03 ` [PATCH] " Chris Wilson
2018-11-09 10:32 ` Mika Kuoppala
2018-11-09 10:49 ` Chris Wilson [this message]
2018-11-09 9:47 ` ✓ Fi.CI.BAT: success for series starting with drm/i915: Initialise the obj->rcu head (rev2) Patchwork
2018-11-09 13:51 ` ✓ Fi.CI.IGT: " Patchwork
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=154176056755.30559.2472619344322307125@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.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.