On Fri, Jul 7, 2017 at 1:58 PM, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > Quoting Daniel Vetter (2017-07-07 11:17:22) >> On Fri, Mar 17, 2017 at 12:15 PM, Joonas Lahtinen >> <joonas.lahtinen@xxxxxxxxxxxxxxx> wrote: >> > On to, 2017-03-16 at 13:20 +0000, Chris Wilson wrote: >> >> Currently, the last object in the execlist is the always the batch. >> >> However, when building the batch buffer we often know the batch object >> >> first and if we can use the first slot in the execlist we can emit >> >> relocation instructions relative to it immediately and avoid a separate >> >> pass to adjust the relocations to point to the last execlist slot. >> >> >> >> Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> >> > >> > Reviewed-by: Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx> >> >> This patch was reviewed/pushed full month before the mesa patch was >> fully reviewed and ready for merging. That's not how uapi is done. >> >> I've fixed this up now by at least reviewing the mesa patch, but for >> next time around: If you review uapi, and you don't make sure the >> userspace side is in good shape too, then you've not reviewed the >> patch properly. > > The userspace was in good shape and had been requested. Now explain the > complication in the API that merits a rant? > > You've had well over 2 years to review the patches that first used it. uapi merge rules: 1. get everything reviewed, tested and everything ready for merging 2. merge kernel side 3. merge userpsace side This here very much looked liked the userspace side wasn't ready yet, and the kernel side was pushed already. This is the reviewers&committers job to ensure, not mine, so no idea why I've had over 2 years to review things ... Anyway, should we add some checks for uapi additions to dim? Just checking for a Testcase: or References: line for the userspace might be useful, but then many uapi additions don't touch include/uapi ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
