From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 0/7] gtt patches
Date: Fri, 27 Sep 2013 12:29:26 -0700 [thread overview]
Message-ID: <20130927192926.GA1057@bwidawsk.net> (raw)
In-Reply-To: <CAKMK7uHrj2S_D5NQ9ZXZ=kpFe2PuYG0U-eXzqr=X55mHB3Appw@mail.gmail.com>
On Fri, Sep 27, 2013 at 09:21:51PM +0200, Daniel Vetter wrote:
> On Fri, Sep 27, 2013 at 7:34 AM, Ben Widawsky <ben@bwidawsk.net> wrote:
> > At this point it just seems like you're intentionally making it harder
> > for me to ever merge PPGTT.
>
> I have two issues with the merged patches:
> 1. There's a regression, and QA is meanwhile at the 3rd or so dupe
> report. So it's not really an arcane corner case. And I've
> specifically written a testcase for secure batch dispatching and
> specifically asked you to test to make sure it catches the bugs we've
> discussed, so I hope you understand I'm a bit underwhelmed that this
> slept through.
>
> 2. I have a bit an issue with the currently merged code for rebasing
> -internal. I only stumbled over that when I've tried to rebase
> -internal and was a bit disappointed to see that despite that I've
> raised this the first time your vm->bind/unbind patches showed up
> nothing changed.
>
> That's the first&last patch.
>
> The stuff in-between is to make rebasing -internal a bit easier (while
> I need to do fixups anyway) since I really botched this 1-2 times
> everytime there was a conflict. I've thought that the oustanding stuff
> from your series only needs to touch the ->enable callbacks in
> i915_gem_gtt.c. A quick look at your ppgtt branches shows that in
> addition to that there's only a now outdated cleanup patch and a
> rather self-contained debugfs dumper on top. So my thinking was that
> right now is an ideal time to polish i915_gem_gtt.c a bit.
>
> But of course I'll drop cleanup patches when they conflict badly with
> ongoing stuff, like I've done a few times already. But it didn't look
> like this is the case here.
>
> Now you seem to reject my patches, but I don't see any alternate
> proposals from you. Furthermore to me it feels a bit the discussion
> has derailed into non-constructive form a bit, so I guess this will
> take a bit of time to resolve. Since I can't just hold public and
> internal trees hostage until that's settled I'll drop your two vma
> patches meanwhile.
>
> Cheers, Daniel
I do not plan to develop PPGTT any further. Please feel free to revert
as many patches as you'd like.
--
Ben Widawsky, Intel Open Source Technology Center
prev parent reply other threads:[~2013-09-27 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 20:31 [PATCH 0/7] gtt patches Daniel Vetter
2013-09-26 20:31 ` [PATCH 1/7] drm/i915: resurrect ->insert_entries/->clear_range gtt interfaces Daniel Vetter
2013-09-26 20:31 ` [PATCH 2/7] drm/i915: don't allow ppgtt enabling to fail anymore Daniel Vetter
2013-09-26 20:31 ` [PATCH 3/7] drm/i915/gtt: group sg setup/teardown functions to the end Daniel Vetter
2013-09-26 20:31 ` [PATCH 4/7] drm/i915/gtt: move restore_gtt_mappings to the bottom Daniel Vetter
2013-09-26 20:31 ` [PATCH 5/7] drm/i915/gtt: group legacy global gtt code together Daniel Vetter
2013-09-26 20:31 ` [PATCH 6/7] drm/i915/gtt: move generic setup code all to the bottom Daniel Vetter
2013-09-26 20:31 ` [PATCH 7/7] drm/i915: we can't call move_to_active before intel_ring_begin Daniel Vetter
2013-09-27 5:34 ` [PATCH 0/7] gtt patches Ben Widawsky
2013-09-27 19:21 ` Daniel Vetter
2013-09-27 19:29 ` Ben Widawsky [this message]
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=20130927192926.GA1057@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox