From: Daniel Vetter <daniel@ffwll.ch>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: gvt gem fixes
Date: Thu, 20 Oct 2016 09:02:45 +0200 [thread overview]
Message-ID: <20161020070245.GN20761@phenom.ffwll.local> (raw)
In-Reply-To: <20161020003305.ymwtv2h2vswx37jc@zhen-hp.sh.intel.com>
On Thu, Oct 20, 2016 at 08:33:05AM +0800, Zhenyu Wang wrote:
> On 2016.10.19 12:02:58 +0100, Chris Wilson wrote:
> > On Wed, Oct 19, 2016 at 06:45:51PM +0800, Zhenyu Wang wrote:
> > > On 2016.10.19 11:11:35 +0100, Chris Wilson wrote:
> > > > I think this is the set required to bring gvt into line, at least to
> > > > unblock myself.
> > >
> > > Thanks a lot, Chris. I'd like to merge this in next pull request,
> > > or let me know you want to be picked up by drm-intel directly.
> > > If 4/12 would be picked up alone, I'll skip that one in gvt tree.
> >
> > If you are confident in having the pull ready in the next day or so,
> > I'll just preface my series with these and they will evaporate after the
> > merge.
> >
>
> I'll try to send it today.
>
> > I'll apply 4/12 right now to get that out of the way.
>
> ok, fine.
Yeah, I think anything that touches i915 code should get merged through
drm-intel directly with the usual process. Only exception is when gvt has
a functional depency and it's a small patch, then I think we can sometimes
merge i915 core patches through gvt, with an ack from Jani or me (and
still proper review and CI and everything ofc). But that should be the
rare exception.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-10-20 7:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 10:11 gvt gem fixes Chris Wilson
2016-10-19 10:11 ` [PATCH 01/12] drm/i915/gvt: s/drm_gem_object_unreference/i915_gem_object_put/ Chris Wilson
2016-10-19 10:11 ` [PATCH 02/12] drm/i915/gvt: Add runtime pm around fences Chris Wilson
2016-10-19 10:11 ` [PATCH 03/12] drm/i915/gvt: i915_gem_object_create() returns an error pointer Chris Wilson
2016-10-19 10:11 ` [PATCH 04/12] drm/i915: Catch premature unpinning of pages Chris Wilson
2016-10-19 10:26 ` Joonas Lahtinen
2016-10-19 10:11 ` [PATCH 05/12] drm/i915/gvt: Use the returned VMA to provide the virtual address Chris Wilson
2016-10-19 10:11 ` [PATCH 06/12] drm/i915/gvt: Remove dangerous unpin of backing storage of bound GPU object Chris Wilson
2016-10-19 10:11 ` [PATCH 07/12] drm/i915/gvt: Hold a reference on the request Chris Wilson
2016-10-19 10:32 ` Zhenyu Wang
2016-10-19 10:53 ` Chris Wilson
2016-10-20 0:22 ` Zhenyu Wang
2016-10-20 6:52 ` Chris Wilson
2016-10-20 7:33 ` Zhenyu Wang
2016-10-19 10:11 ` [PATCH 08/12] drm/i915/gvt: Stop checking for impossible interrupts from a kthread Chris Wilson
2016-10-19 10:11 ` [PATCH 09/12] drm/i915/gvt: Stop waiting whilst holding struct_mutex Chris Wilson
2016-10-19 10:11 ` [PATCH 10/12] drm/i915/gvt: Use common mapping routines for indirect_ctx object Chris Wilson
2016-10-19 10:26 ` Zhenyu Wang
2016-10-19 10:11 ` [PATCH 11/12] drm/i915/gvt: Use common mapping routines for shadow_bb object Chris Wilson
2016-10-19 10:11 ` [PATCH 12/12] drm/i915/gvt: Remove defunct vmap_batch() Chris Wilson
2016-10-19 10:45 ` gvt gem fixes Zhenyu Wang
2016-10-19 11:02 ` Chris Wilson
2016-10-20 0:33 ` Zhenyu Wang
2016-10-20 7:02 ` Daniel Vetter [this message]
2016-10-20 7:15 ` Zhenyu Wang
2016-10-20 9:13 ` Daniel Vetter
2016-10-19 13:54 ` ✗ Fi.CI.BAT: warning for series starting with [01/12] drm/i915/gvt: s/drm_gem_object_unreference/i915_gem_object_put/ 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=20161020070245.GN20761@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox