Re: [Intel-gfx] linux-next: manual merge of the drm-misc tree with the admgpu tree

Hi all, This is now a conflict between the amdgpu tree and the drm tree. On Fri, 4 Oct 2019 11:10:22 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the drm-misc tree got a conflict in: > > drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c > > between commit: > >

Re: [Intel-gfx] linux-next: build failure after merge of the drm-misc tree

Hi all, This is now a semantic conflict between the drm and v4l-dvb trees. On Tue, 8 Oct 2019 10:30:45 +1100 Stephen Rothwell wrote: > > After merging the drm-misc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: drivers/media/platform/cec-gpio/cec-gpio.c: In function

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/execlists: Tweak virtual unsubmission

== Series Details == Series: drm/i915/execlists: Tweak virtual unsubmission URL : https://patchwork.freedesktop.org/series/67958/ State : warning == Summary == $ dim checkpatch origin/drm-tip 3b2b0acd537f drm/i915/execlists: Tweak virtual unsubmission -:14: WARNING:COMMIT_LOG_LONG_LINE:

[Intel-gfx] [PATCH] drm/i915/execlists: Tweak virtual unsubmission

Since commit e2144503bf3b ("drm/i915: Prevent bonded requests from overtaking each other on preemption") we have restricted requests to run on their chosen engine across preemption events. We can take this restriction into account to know that we will want to resubmit those requests onto the same

[Intel-gfx] [PATCH] drm/i915/execlists: Assert tasklet is locked for process_csb()

We rely on only the tasklet being allowed to call into process_csb(), so assert that is locked when we do. As the tasklet uses a simple bitlock, there is no strong lockdep checking so we must make do with a plain assertion that the tasklet is running and assume that we are the tasklet!

Re: [Intel-gfx] [PATCH] kernel-doc: rename the kernel-doc directive 'functions' to 'specific'

Hi Changbin, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [cannot apply to v5.4-rc2 next-20191010] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to

[Intel-gfx] [PATCH] drm/i915/execlists: Clear semaphore immediately upon ELSP promotion

There is no significance to our delay before clearing the semaphore the engine is waiting on, so release it as soon as we acknowledge the CS update following our preemption request. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/gt/intel_lrc.c | 6 +++--- 1 file changed, 3 insertions(+),

[Intel-gfx] [PATCH i-g-t 1/2] lib: Generalise rapl interface

We can use our existing rapl interface that monitors gpu power, to also sample the other rapl domains such as package, cores and ram. Signed-off-by: Chris Wilson Cc: Andi Shyti --- lib/Makefile.sources| 4 +- lib/igt_gpu_power.c | 87

[Intel-gfx] [PATCH i-g-t 2/2] overlay: Show total package power

Add the total package power after the GPU package power, for reference. Signed-off-by: Chris Wilson --- overlay/overlay.c | 18 ++ overlay/power.c | 88 +++ overlay/power.h | 21 +-- 3 files changed, 59 insertions(+), 68

[Intel-gfx] [PATCH v2] drm/i915/selftests: Fixup naked 64b divide

drivers/gpu/drm/i915/intel_memory_region.o: in function `igt_mock_contiguous': drivers/gpu/drm/i915/selftests/intel_memory_region.c:166: undefined reference to `__umoddi3' v2: promote target to u64 for consistency across all builds Reported-by: kbuild test robot Fixes: 2f0b97ca0211

Re: [Intel-gfx] [PATCH] drm/i915/perf: Avoid polluting the i915_oa_config with error pointers

On 13/10/2019 12:52, Chris Wilson wrote: Use a local variable to track the allocation errors to avoid polluting the struct and keep the free simple. Reported-by: kbuild test robot Reported-by: Dan Carpenter Signed-off-by: Chris Wilson Cc: Lionel Landwerlin Reviewed-by: Lionel Landwerlin

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gem: Distinguish each object type

== Series Details == Series: drm/i915/gem: Distinguish each object type URL : https://patchwork.freedesktop.org/series/67948/ State : success == Summary == CI Bug Log - changes from CI_DRM_7075 -> Patchwork_14781 Summary ---

[Intel-gfx] ✗ Fi.CI.BUILD: warning for drm/i915/selftests: Fixup naked 64b divide

== Series Details == Series: drm/i915/selftests: Fixup naked 64b divide URL : https://patchwork.freedesktop.org/series/67947/ State : warning == Summary == CALLscripts/checksyscalls.sh CALLscripts/atomic/check-atomics.sh CHK include/generated/compile.h AR

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Fixup naked 64b divide

== Series Details == Series: drm/i915/selftests: Fixup naked 64b divide URL : https://patchwork.freedesktop.org/series/67947/ State : success == Summary == CI Bug Log - changes from CI_DRM_7075 -> Patchwork_14780 Summary ---

[Intel-gfx] [PATCH] drm/i915/perf: Avoid polluting the i915_oa_config with error pointers

Use a local variable to track the allocation errors to avoid polluting the struct and keep the free simple. Reported-by: kbuild test robot Reported-by: Dan Carpenter Signed-off-by: Chris Wilson Cc: Lionel Landwerlin --- drivers/gpu/drm/i915/i915_perf.c | 52 +++-

[Intel-gfx] [PATCH] drm/i915/gem: Distinguish each object type

Separate each object class into a separate lock type to avoid lockdep cross-contamination between paths (i.e. userptr!). Signed-off-by: Chris Wilson Cc: Matthew Auld --- drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c | 3 ++- drivers/gpu/drm/i915/gem/i915_gem_internal.c | 3 ++-

[Intel-gfx] [PATCH] drm/i915/selftests: Fixup naked 64b divide

drivers/gpu/drm/i915/intel_memory_region.o: in function `igt_mock_contiguous': drivers/gpu/drm/i915/selftests/intel_memory_region.c:166: undefined reference to `__umoddi3' Reported-by: kbuild test robot Fixes: 2f0b97ca0211 ("drm/i915/region: support contiguous allocations") Signed-off-by: Chris