Re: [Intel-gfx] [PATCH] drm/i915/gem: use spinlock_t instead of struct spinlock

On Mon, 17 Feb 2020, Chris Wilson wrote: > Quoting Jani Nikula (2020-02-17 18:42:19) >> spinlock_t is one case where the typedef is to be preferred over struct >> spinlock. >> >> Fixes: 42fb60de3129 ("drm/i915/gem: Don't leak non-persistent requests on >> changing engines") >> Cc: Chris Wilson

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/gt: Declare when we enabled timeslicing

== Series Details == Series: drm/i915/gt: Declare when we enabled timeslicing URL : https://patchwork.freedesktop.org/series/73490/ State : success == Summary == CI Bug Log - changes from CI_DRM_7943_full -> Patchwork_16580_full Summary

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/gt: Declare when we enabled timeslicing

== Series Details == Series: series starting with [1/2] drm/i915/gt: Declare when we enabled timeslicing URL : https://patchwork.freedesktop.org/series/73489/ State : success == Summary == CI Bug Log - changes from CI_DRM_7943_full -> Patchwork_16579_full

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Init lspcon after HPD in intel_dp_detect()

== Series Details == Series: drm/i915: Init lspcon after HPD in intel_dp_detect() URL : https://patchwork.freedesktop.org/series/73480/ State : success == Summary == CI Bug Log - changes from CI_DRM_7942_full -> Patchwork_16576_full

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/csr: use intel_de_*() functions for register access

== Series Details == Series: series starting with [1/2] drm/i915/csr: use intel_de_*() functions for register access URL : https://patchwork.freedesktop.org/series/73473/ State : success == Summary == CI Bug Log - changes from CI_DRM_7942_full -> Patchwork_16575_full

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [CI,1/2] drm/i915: split intel_modeset_driver_remove() to pre/post irq uninstall

== Series Details == Series: series starting with [CI,1/2] drm/i915: split intel_modeset_driver_remove() to pre/post irq uninstall URL : https://patchwork.freedesktop.org/series/73469/ State : success == Summary == CI Bug Log - changes from CI_DRM_7942_full -> Patchwork_16574_full

[Intel-gfx] ✓ Fi.CI.IGT: success for Adding definitions for VRR registers and bitfields (rev2)

== Series Details == Series: Adding definitions for VRR registers and bitfields (rev2) URL : https://patchwork.freedesktop.org/series/73398/ State : success == Summary == CI Bug Log - changes from CI_DRM_7939_full -> Patchwork_16572_full

Re: [Intel-gfx] [PATCH] drm/i915/gem: use spinlock_t instead of struct spinlock

Quoting Jani Nikula (2020-02-17 18:42:19) > spinlock_t is one case where the typedef is to be preferred over struct > spinlock. > > Fixes: 42fb60de3129 ("drm/i915/gem: Don't leak non-persistent requests on > changing engines") > Cc: Chris Wilson > Cc: Tvrtko Ursulin > Signed-off-by: Jani

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gem: use spinlock_t instead of struct spinlock

== Series Details == Series: drm/i915/gem: use spinlock_t instead of struct spinlock URL : https://patchwork.freedesktop.org/series/73546/ State : success == Summary == CI Bug Log - changes from CI_DRM_7957 -> Patchwork_16595 Summary

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/selftests: Check for the error interrupt before we wait!

== Series Details == Series: drm/i915/selftests: Check for the error interrupt before we wait! URL : https://patchwork.freedesktop.org/series/73461/ State : success == Summary == CI Bug Log - changes from CI_DRM_7939_full -> Patchwork_16571_full

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [CI,v3,1/3] drm/i915: Introduce encoder->compute_config_late()

== Series Details == Series: series starting with [CI,v3,1/3] drm/i915: Introduce encoder->compute_config_late() URL : https://patchwork.freedesktop.org/series/73460/ State : success == Summary == CI Bug Log - changes from CI_DRM_7939_full -> Patchwork_16570_full

Re: [Intel-gfx] [PATCH 5/5] drm/amdgpu: implement amdgpu_gem_prime_move_notify v2

On Mon, Feb 17, 2020 at 7:58 PM Christian König wrote: > > Am 17.02.20 um 18:55 schrieb Daniel Vetter: > > On Mon, Feb 17, 2020 at 04:45:09PM +0100, Christian König wrote: > >> Implement the importer side of unpinned DMA-buf handling. > >> > >> v2: update page tables immediately > >> > >>

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gt: make a gt sysfs group and move power management files (rev3)

== Series Details == Series: drm/i915/gt: make a gt sysfs group and move power management files (rev3) URL : https://patchwork.freedesktop.org/series/73190/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7939_full -> Patchwork_16569_full

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gem: use spinlock_t instead of struct spinlock

== Series Details == Series: drm/i915/gem: use spinlock_t instead of struct spinlock URL : https://patchwork.freedesktop.org/series/73546/ State : warning == Summary == $ dim checkpatch origin/drm-tip 7042c07be74c drm/i915/gem: use spinlock_t instead of struct spinlock -:23:

[Intel-gfx] [PATCH] drm/i915/gem: use spinlock_t instead of struct spinlock

spinlock_t is one case where the typedef is to be preferred over struct spinlock. Fixes: 42fb60de3129 ("drm/i915/gem: Don't leak non-persistent requests on changing engines") Cc: Chris Wilson Cc: Tvrtko Ursulin Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/gem/i915_gem_context_types.h

[Intel-gfx] ✗ Fi.CI.IGT: failure for Add support for Color encoding YCBCR_BT2020

== Series Details == Series: Add support for Color encoding YCBCR_BT2020 URL : https://patchwork.freedesktop.org/series/73457/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7938_full -> Patchwork_16568_full Summary ---

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/gt: Yield the timeslice if caught waiting on a user semaphore

== Series Details == Series: series starting with [1/2] drm/i915/gt: Yield the timeslice if caught waiting on a user semaphore URL : https://patchwork.freedesktop.org/series/73455/ State : success == Summary == CI Bug Log - changes from CI_DRM_7938_full -> Patchwork_16566_full

Re: [Intel-gfx] [PATCH 5/5] drm/amdgpu: implement amdgpu_gem_prime_move_notify v2

On Mon, Feb 17, 2020 at 04:45:09PM +0100, Christian König wrote: > Implement the importer side of unpinned DMA-buf handling. > > v2: update page tables immediately > > Signed-off-by: Christian König > --- > drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c | 66 - >

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Cast remain to unsigned long in eb_relocate_vma

== Series Details == Series: drm/i915: Cast remain to unsigned long in eb_relocate_vma URL : https://patchwork.freedesktop.org/series/73440/ State : success == Summary == CI Bug Log - changes from CI_DRM_7936_full -> Patchwork_16565_full

[Intel-gfx] [drm-intel:drm-intel-next-queued 1/2] drivers/gpu/drm/i915/gt/intel_lrc.c:1224:3: note: in expansion of macro 'I915_SELFTEST_ONLY'

Hi Tvrtko, FYI, the error/warning still remains. tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued head: d194314da04eb965c651dcef6d692dc83821a414 commit: 1883a0a4658eaba354db2179b4d3395247d27582 [1/2] drm/i915: Track hw reported context runtime config: i386-defconfig

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftest: Analyse timestamp behaviour across context switches (rev2)

== Series Details == Series: drm/i915/selftest: Analyse timestamp behaviour across context switches (rev2) URL : https://patchwork.freedesktop.org/series/73536/ State : success == Summary == CI Bug Log - changes from CI_DRM_7954 -> Patchwork_16594

[Intel-gfx] ✓ Fi.CI.IGT: success for lib: Add a YAML emitter

== Series Details == Series: lib: Add a YAML emitter URL : https://patchwork.freedesktop.org/series/73433/ State : success == Summary == CI Bug Log - changes from CI_DRM_7935_full -> Patchwork_16563_full Summary --- **SUCCESS**

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Mark the mock ring->vma as being in the GGTT

On Sat, 15 Feb 2020 at 20:59, Chris Wilson wrote: > > The ringbuffer's vma is expected to be in the GGTT and that is now being > checked, so make sure the mocked ring declares it so. > > Signed-off-by: Chris Wilson Reviewed-by: Matthew Auld ___

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: Rearrange code to silence compiler

== Series Details == Series: drm/i915/gt: Rearrange code to silence compiler URL : https://patchwork.freedesktop.org/series/73533/ State : success == Summary == CI Bug Log - changes from CI_DRM_7954 -> Patchwork_16593 Summary ---

[Intel-gfx] ✓ Fi.CI.BAT: success for Introduce CAP_PERFMON to secure system performance monitoring and observability (rev4)

== Series Details == Series: Introduce CAP_PERFMON to secure system performance monitoring and observability (rev4) URL : https://patchwork.freedesktop.org/series/72273/ State : success == Summary == CI Bug Log - changes from CI_DRM_7954 -> Patchwork_16592

Re: [Intel-gfx] [PATCH 1/6] drm/i915: Introduce proper dbuf state

On Mon, Feb 17, 2020 at 08:46:40AM +, Lisovskiy, Stanislav wrote: > On Thu, 2020-02-13 at 20:47 +0200, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Add a global state to track the dbuf slices. Gets rid of all the > > nasty > > coupling between state->modeset and dbuf recompulation.

Re: [Intel-gfx] [PATCH v2 5/7] drm/i915: Get first crtc instead of PIPE_A crtc

On Mon, Feb 17, 2020 at 10:52:28AM +0530, Anshuman Gupta wrote: > On 2020-02-11 at 22:55:30 +0530, Anshuman Gupta wrote: > > intel_plane_fb_max_stride should return the max stride of > > primary plane for first available pipe in intel device info > > pipe_mask. > > Similarly

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Proper dbuf global state

== Series Details == Series: drm/i915: Proper dbuf global state URL : https://patchwork.freedesktop.org/series/73421/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7934_full -> Patchwork_16562_full Summary ---

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftest: Analyse timestamp behaviour across context switches (rev2)

== Series Details == Series: drm/i915/selftest: Analyse timestamp behaviour across context switches (rev2) URL : https://patchwork.freedesktop.org/series/73536/ State : warning == Summary == $ dim checkpatch origin/drm-tip 2efef231d1a5 drm/i915/selftest: Analyse timestamp behaviour across

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/gt: Ensure 'ENABLE_BOOT_FETCH' is enabled before ppGTT

== Series Details == Series: series starting with [1/2] drm/i915/gt: Ensure 'ENABLE_BOOT_FETCH' is enabled before ppGTT URL : https://patchwork.freedesktop.org/series/73419/ State : success == Summary == CI Bug Log - changes from CI_DRM_7933_full -> Patchwork_16561_full

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce CAP_PERFMON to secure system performance monitoring and observability (rev4)

== Series Details == Series: Introduce CAP_PERFMON to secure system performance monitoring and observability (rev4) URL : https://patchwork.freedesktop.org/series/72273/ State : warning == Summary == $ dim checkpatch origin/drm-tip 393a5cfde640 capabilities: introduce CAP_PERFMON to kernel

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/selftests: Exercise timeslice rewinding (rev2)

== Series Details == Series: drm/i915/selftests: Exercise timeslice rewinding (rev2) URL : https://patchwork.freedesktop.org/series/73198/ State : success == Summary == CI Bug Log - changes from CI_DRM_7932_full -> Patchwork_16558_full

[Intel-gfx] [PATCH] drm/i915/selftest: Analyse timestamp behaviour across context switches

Check that the CTX_TIMESTAMP is monotonic across context save/restore and upon preemption. References: https://gitlab.freedesktop.org/drm/intel/issues/1233 Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/gt/selftest_lrc.c | 230 + 1 file changed, 230 insertions(+)

[Intel-gfx] ✓ Fi.CI.IGT: success for Revert "drm/i915: Update dbuf slices only with full modeset"

== Series Details == Series: Revert "drm/i915: Update dbuf slices only with full modeset" URL : https://patchwork.freedesktop.org/series/73412/ State : success == Summary == CI Bug Log - changes from CI_DRM_7932_full -> Patchwork_16557_full

[Intel-gfx] [PATCH] drm/i915/selftest: Analyse timestamp behaviour across context switches

Check that the CTX_TIMESTAMP is monotonic across context save/restore and upon preemption. References: https://gitlab.freedesktop.org/drm/intel/issues/1233 Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/gt/selftest_lrc.c | 229 + 1 file changed, 229 insertions(+)

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dsc: force full modeset whenever DSC is enabled at probe

== Series Details == Series: drm/i915/dsc: force full modeset whenever DSC is enabled at probe URL : https://patchwork.freedesktop.org/series/73410/ State : success == Summary == CI Bug Log - changes from CI_DRM_7932_full -> Patchwork_16556_full

[Intel-gfx] ✓ Fi.CI.IGT: success for Fix state transitions affecting DBuf

== Series Details == Series: Fix state transitions affecting DBuf URL : https://patchwork.freedesktop.org/series/73406/ State : success == Summary == CI Bug Log - changes from CI_DRM_7932_full -> Patchwork_16554_full Summary ---

Re: [Intel-gfx] [PATCH] drm: bugs.freedesktop.org is no longer accepting bugs

On Tue, 14 Jan 2020, Christian Kujau wrote: > Hello, > > this should apply cleanly to drm-tip. > > > drm: bugs.freedesktop.org is no longer accepting bugs. > > freedesktop.org Bugzilla is no longer in use and new DRM bugs > should be reported to

Re: [Intel-gfx] [PATCH] drm/i915/gt: Rearrange code to silence compiler

On 17/02/2020 09:58, Chris Wilson wrote: Without selftests enabled, I915_SELFTEST_ONLY becomes a dummy, generating a bare '0'. This causes the compiler to complain about a useless line, and while we could use I915_SELFTEST_DECLARE instead, it is a bit messier. Move the selftest-only code to a

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gt: Suppress warnings for unused debugging locals

== Series Details == Series: drm/i915/gt: Suppress warnings for unused debugging locals URL : https://patchwork.freedesktop.org/series/73394/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7930_full -> Patchwork_16552_full

[Intel-gfx] [PATCH] drm/i915/gt: Rearrange code to silence compiler

Without selftests enabled, I915_SELFTEST_ONLY becomes a dummy, generating a bare '0'. This causes the compiler to complain about a useless line, and while we could use I915_SELFTEST_DECLARE instead, it is a bit messier. Move the selftest-only code to a helper and make that conditional on having

Re: [Intel-gfx] [PATCH 2/2] drm/i915: switch vlv_suspend to use intel uncore register accessors

On Thu, 13 Feb 2020, Chris Wilson wrote: > Quoting Jani Nikula (2020-02-12 14:40:58) >> Prefer intel_uncore_* over I915_READ, I915_WRITE, and POSTING_READ. >> >> Signed-off-by: Jani Nikula > > A couple of older checkpatch errors that could be cleaned up (pure > whitespacing). > > Both >

Re: [Intel-gfx] [PATCH 2/2] drm/i915: Update drm/i915 bug filing URL

On Thu, 13 Feb 2020, Chris Wilson wrote: > Quoting Jani Nikula (2020-02-12 16:04:34) >> We've moved from bugzilla to gitlab. >> >> Cc: sta...@vger.kernel.org >> Signed-off-by: Jani Nikula > > Hopefully the extra how-to-file-a-bug appeases Martin, > Both, > Reviewed-by: Chris Wilson Thanks,

Re: [Intel-gfx] [PATCH 1/6] drm/i915: Introduce proper dbuf state

On Thu, 2020-02-13 at 20:47 +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Add a global state to track the dbuf slices. Gets rid of all the > nasty > coupling between state->modeset and dbuf recompulation. Also we can > now > totally nuke state->active_pipe_changes. > >

[Intel-gfx] [PATCH v7 12/12] doc/admin-guide: update kernel.rst with CAP_PERFMON information

Update kernel.rst documentation file with the information related to usage of CAP_PERFMON capability to secure performance monitoring and observability operations in system. Signed-off-by: Alexey Budankov --- Documentation/admin-guide/sysctl/kernel.rst | 16 +++- 1 file changed,

[Intel-gfx] [PATCH v7 11/12] doc/admin-guide: update perf-security.rst with CAP_PERFMON information

Update perf-security.rst documentation file with the information related to usage of CAP_PERFMON capability to secure performance monitoring and observability operations in system. Signed-off-by: Alexey Budankov --- Documentation/admin-guide/perf-security.rst | 65 + 1

[Intel-gfx] [PATCH v7 10/12] drivers/oprofile: open access for CAP_PERFMON privileged process

Open access to monitoring for CAP_PERFMON privileged process. Providing the access under CAP_PERFMON capability singly, without the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the credentials and makes operation more secure. CAP_PERFMON implements the principal of least

[Intel-gfx] [PATCH v7 09/12] drivers/perf: open access for CAP_PERFMON privileged process

Open access to monitoring for CAP_PERFMON privileged process. Providing the access under CAP_PERFMON capability singly, without the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the credentials and makes operation more secure. CAP_PERFMON implements the principal of least

[Intel-gfx] [PATCH v7 08/12] parisc/perf: open access for CAP_PERFMON privileged process

Open access to monitoring for CAP_PERFMON privileged process. Providing the access under CAP_PERFMON capability singly, without the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the credentials and makes operation more secure. CAP_PERFMON implements the principal of least

[Intel-gfx] [PATCH v7 07/12] powerpc/perf: open access for CAP_PERFMON privileged process

Open access to monitoring for CAP_PERFMON privileged process. Providing the access under CAP_PERFMON capability singly, without the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the credentials and makes operation more secure. CAP_PERFMON implements the principal of least

[Intel-gfx] [PATCH v7 06/12] trace/bpf_trace: open access for CAP_PERFMON privileged process

Open access to bpf_trace monitoring for CAP_PERFMON privileged process. Providing the access under CAP_PERFMON capability singly, without the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the credentials and makes operation more secure. CAP_PERFMON implements the principal of

[Intel-gfx] [PATCH v7 04/12] perf tool: extend Perf tool with CAP_PERFMON capability support

Extend error messages to mention CAP_PERFMON capability as an option to substitute CAP_SYS_ADMIN capability for secure system performance monitoring and observability. Make perf_event_paranoid_check() and __cmd_ftrace() to be aware of CAP_PERFMON capability. CAP_PERFMON implements the principal

[Intel-gfx] [PATCH v7 05/12] drm/i915/perf: open access for CAP_PERFMON privileged process

Open access to i915_perf monitoring for CAP_PERFMON privileged process. Providing the access under CAP_PERFMON capability singly, without the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the credentials and makes operation more secure. CAP_PERFMON implements the principal of

[Intel-gfx] [PATCH v7 03/12] perf/core: open access to probes for CAP_PERFMON privileged process

Open access to monitoring via kprobes and uprobes and eBPF tracing for CAP_PERFMON privileged process. Providing the access under CAP_PERFMON capability singly, without the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the credentials and makes operation more secure. perf

[Intel-gfx] [PATCH v7 02/12] perf/core: open access to the core for CAP_PERFMON privileged process

Open access to monitoring of kernel code, cpus, tracepoints and namespaces data for a CAP_PERFMON privileged process. Providing the access under CAP_PERFMON capability singly, without the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the credentials and makes operation more

[Intel-gfx] [PATCH v7 01/12] capabilities: introduce CAP_PERFMON to kernel and user space

Introduce CAP_PERFMON capability designed to secure system performance monitoring and observability operations so that CAP_PERFMON would assist CAP_SYS_ADMIN capability in its governing role for performance monitoring and observability subsystems. CAP_PERFMON hardens system security and

[Intel-gfx] [PATCH v7 00/12] Introduce CAP_PERFMON to secure system performance monitoring and observability

Currently access to perf_events, i915_perf and other performance monitoring and observability subsystems of the kernel is open only for a privileged process [1] with CAP_SYS_ADMIN capability enabled in the process effective set [2]. This patch set introduces CAP_PERFMON capability designed to