From: "Du, Changbin" <changbin.du@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
changbin.du@intel.com, intel-gvt-dev@lists.freedesktop.org,
daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: make context status notifier head be per engine
Date: Fri, 17 Mar 2017 10:28:51 +0800 [thread overview]
Message-ID: <20170317022850.GA3573@intel.com> (raw)
In-Reply-To: <20170316162823.GB2118@nuc-i3427.alporthouse.com>
[-- Attachment #1.1: Type: text/plain, Size: 900 bytes --]
> > > Since intel_gvt_init() is called at early initialization stage and
> > > require the status notifier head has been initiated, I initiate it in
> > > intel_engine_setup().
> > >
> > > v2: remove a redundant newline. (chris)
> > >
> > > Signed-off-by: Changbin Du <changbin.du@intel.com>
> > > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> >
> > Applied to gvt-next, thanks!
>
> It turns out this fixes a use-after-free bug that CI was falling over.
> Applied to dinq.
>
wow, that's out of my expectation. lucky!
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=100232
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
> _______________________________________________
> intel-gvt-dev mailing list
> intel-gvt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev
--
Thanks,
Changbin Du
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-17 2:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 11:23 [RFC PATCH] drm/i915: make context status notifier head be per engine changbin.du
2017-03-02 11:47 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-03-09 8:44 ` [RFC PATCH] " Du, Changbin
2017-03-09 11:27 ` [PATCH] " changbin.du
2017-03-10 17:17 ` Chris Wilson
2017-03-13 2:14 ` Du, Changbin
2017-03-13 2:47 ` [PATCH v2] " changbin.du
2017-03-13 4:03 ` Zhenyu Wang
2017-03-16 16:28 ` Chris Wilson
2017-03-17 2:28 ` Du, Changbin [this message]
2017-03-09 15:22 ` ✓ Fi.CI.BAT: success for drm/i915: make context status notifier head be per engine (rev2) Patchwork
2017-03-13 4:25 ` ✗ Fi.CI.BAT: failure for drm/i915: make context status notifier head be per engine (rev3) 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=20170317022850.GA3573@intel.com \
--to=changbin.du@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=zhenyuw@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.