[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/3] drm/i915: Make exclusive awaits on i915_active optional

== Series Details == Series: series starting with [1/3] drm/i915: Make exclusive awaits on i915_active optional URL : https://patchwork.freedesktop.org/series/75505/ State : success == Summary == CI Bug Log - changes from CI_DRM_8254_full -> Patchwork_17213_full

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gt: move remaining debugfs interfaces into gt (rev5)

== Series Details == Series: drm/i915/gt: move remaining debugfs interfaces into gt (rev5) URL : https://patchwork.freedesktop.org/series/75333/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8254_full -> Patchwork_17212_full

Re: [Intel-gfx] [Mesa-dev] gitlab.fd.o financial situation and impact on services

On Sat, Apr 4, 2020 at 11:41 AM Rob Clark wrote: > > On Sat, Apr 4, 2020 at 11:16 AM Rob Clark wrote: > > > > On Sat, Apr 4, 2020 at 10:47 AM Nicolas Dufresne > > wrote: > > > > > > Le samedi 04 avril 2020 à 08:11 -0700, Rob Clark a écrit : > > > > On Fri, Apr 3, 2020 at 7:12 AM Michel Dänzer

Re: [Intel-gfx] [Mesa-dev] gitlab.fd.o financial situation and impact on services

On Sat, Apr 4, 2020 at 11:16 AM Rob Clark wrote: > > On Sat, Apr 4, 2020 at 10:47 AM Nicolas Dufresne wrote: > > > > Le samedi 04 avril 2020 à 08:11 -0700, Rob Clark a écrit : > > > On Fri, Apr 3, 2020 at 7:12 AM Michel Dänzer wrote: > > > > On 2020-03-01 6:46 a.m., Marek Olšák wrote: > > > > >

Re: [Intel-gfx] [Mesa-dev] gitlab.fd.o financial situation and impact on services

On Sat, Apr 4, 2020 at 10:47 AM Nicolas Dufresne wrote: > > Le samedi 04 avril 2020 à 08:11 -0700, Rob Clark a écrit : > > On Fri, Apr 3, 2020 at 7:12 AM Michel Dänzer wrote: > > > On 2020-03-01 6:46 a.m., Marek Olšák wrote: > > > > For Mesa, we could run CI only when Marge pushes, so that it's

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Make exclusive awaits on i915_active optional

== Series Details == Series: series starting with [1/3] drm/i915: Make exclusive awaits on i915_active optional URL : https://patchwork.freedesktop.org/series/75505/ State : success == Summary == CI Bug Log - changes from CI_DRM_8254 -> Patchwork_17213

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: move remaining debugfs interfaces into gt (rev5)

== Series Details == Series: drm/i915/gt: move remaining debugfs interfaces into gt (rev5) URL : https://patchwork.freedesktop.org/series/75333/ State : success == Summary == CI Bug Log - changes from CI_DRM_8254 -> Patchwork_17212 Summary

[Intel-gfx] [PATCH 3/3] drm/i915/gem: Wait until the context is finally retired before releasing engines

If we want to percolate information back from the HW, up through the GEM context, we need to wait until the intel_context is scheduled out for the last time. This is handled by the retirement of the intel_context's barrier, i.e. by listening to the pulse after the notional unpin. So wait until the

[Intel-gfx] [PATCH 1/3] drm/i915: Make exclusive awaits on i915_active optional

Later use will require asynchronous waits on the active timelines, but will not utilize an async wait on the exclusive channel. Make the await on the exclusive fence explicit in the selection flags. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/i915_active.c | 7 ---

[Intel-gfx] [PATCH 2/3] drm/i915: Allow asynchronous waits on the i915_active barriers

Allow the caller to also wait upon the barriers stored in i915_active. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/i915_active.c | 60 ++ drivers/gpu/drm/i915/i915_active.h | 1 + 2 files changed, 61 insertions(+) diff --git

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gt: move remaining debugfs interfaces into gt (rev5)

== Series Details == Series: drm/i915/gt: move remaining debugfs interfaces into gt (rev5) URL : https://patchwork.freedesktop.org/series/75333/ State : warning == Summary == $ dim checkpatch origin/drm-tip b1842893326e drm/i915/gt: move remaining debugfs interfaces into gt -:131:

[Intel-gfx] [PATCH v6] drm/i915/gt: move remaining debugfs interfaces into gt

From: Andi Shyti The following interfaces: i915_wedged i915_forcewake_user i915_gem_interrupt i915_rcs_topology i915_sseu_status are dependent on gt values. Put them inside gt/ and drop the "i915_" prefix name. This would be the new structure: dri/0/gt | +-- forcewake_user |

Re: [Intel-gfx] [Mesa-dev] gitlab.fd.o financial situation and impact on services

On Fri, Apr 3, 2020 at 7:12 AM Michel Dänzer wrote: > > On 2020-03-01 6:46 a.m., Marek Olšák wrote: > > For Mesa, we could run CI only when Marge pushes, so that it's a strictly > > pre-merge CI. > > Thanks for the suggestion! I implemented something like this for Mesa: > >

Re: [Intel-gfx] [PATCH 5/6] kernel: better document the use_mm/unuse_mm API contract

On 04/04/2020 12:41, Christoph Hellwig wrote: > Switch the function documentation to kerneldoc comments, and add > WARN_ON_ONCE asserts that the calling thread is a kernel thread and > does not have ->mm set (or has ->mm set in the case of unuse_mm). > > Also give the functions a kthread_ prefix

[Intel-gfx] [drm-tip:drm-tip 9/10] drivers/staging/rtl8712/rtl8712_xmit.c:360:18: error: incompatible pointer types initializing 'struct tx_desc *' with an expression of type 'u8 *' (aka 'unsigned cha

Hi Ville, First bad commit (maybe != root cause): tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip head: 06ddf8dd059d59bc27c24b09a6e500809e619982 commit: 02f01c7089f8aadbf676f8d8aad6e0bccac8c46a [9/10] Merge remote-tracking branch 'drm_intel_push/topic/core-for-CI' into drm-tip

[Intel-gfx] ✗ Fi.CI.IGT: failure for devm_drm_dev_alloc, no more drmm_add_final_kfree (rev3)

== Series Details == Series: devm_drm_dev_alloc, no more drmm_add_final_kfree (rev3) URL : https://patchwork.freedesktop.org/series/75463/ State : failure == Summary == CI Bug Log - changes from CI_DRM_8252_full -> Patchwork_17210_full

[Intel-gfx] [PATCH i-g-t] lib/igt_dummyload: Give the timer thread a RT priority boost

Do not leave it up to the lazy scheduler when the timeout is applied to the batch, force it to be real-time! Signed-off-by: Chris Wilson Cc: Michał Winiarski --- lib/igt_dummyload.c | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/lib/igt_dummyload.c

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/dp_mst: Remove drm_dp_mst_has_audio()

== Series Details == Series: drm/dp_mst: Remove drm_dp_mst_has_audio() URL : https://patchwork.freedesktop.org/series/75488/ State : success == Summary == CI Bug Log - changes from CI_DRM_8252_full -> Patchwork_17209_full Summary ---

[Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [1/6] amdgpu: a NULL ->mm does not mean a thread is a kthread

== Series Details == Series: series starting with [1/6] amdgpu: a NULL ->mm does not mean a thread is a kthread URL : https://patchwork.freedesktop.org/series/75491/ State : failure == Summary == Applying: amdgpu: a NULL ->mm does not mean a thread is a kthread Applying: i915/gvt/kvm: a NULL

[Intel-gfx] improve use_mm / unuse_mm

Hi all, this series improves the use_mm / unuse_mm interface by better documenting the assumptions, and my taking the set_fs manipulations spread over the callers into the core API. ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org

[Intel-gfx] [PATCH 5/6] kernel: better document the use_mm/unuse_mm API contract

Switch the function documentation to kerneldoc comments, and add WARN_ON_ONCE asserts that the calling thread is a kernel thread and does not have ->mm set (or has ->mm set in the case of unuse_mm). Also give the functions a kthread_ prefix to better document the use case. Signed-off-by:

[Intel-gfx] [PATCH 3/6] i915/gvt: remove unused xen bits

No Xen support anywhere here. Remove a dead declaration and an unused include. Signed-off-by: Christoph Hellwig --- drivers/gpu/drm/i915/gvt/gvt.c | 1 - drivers/gpu/drm/i915/gvt/hypercall.h | 2 -- 2 files changed, 3 deletions(-) diff --git a/drivers/gpu/drm/i915/gvt/gvt.c

[Intel-gfx] [PATCH 2/6] i915/gvt/kvm: a NULL ->mm does not mean a thread is a kthread

Use the proper API instead. Fixes: f440c8a572d7 ("drm/i915/gvt/kvmgt: read/write GPA via KVM API") Signed-off-by: Christoph Hellwig --- drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gvt/kvmgt.c

[Intel-gfx] [PATCH 4/6] kernel: move use_mm/unuse_mm to kthread.c

These helpers are only for use with kernel threads, and I will tie them more into the kthread infrastructure going forward. Also move the prototypes to kthread.h - mmu_context.h was a little weird to start with as it otherwise contains very low-level MM bits. Signed-off-by: Christoph Hellwig

[Intel-gfx] [PATCH 1/6] amdgpu: a NULL ->mm does not mean a thread is a kthread

Use the proper API instead. Fixes: 70539bd795002 ("drm/amd: Update MEC HQD loading code for KFD") Signed-off-by: Christoph Hellwig --- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h

[Intel-gfx] [PATCH 6/6] kernel: set USER_DS in kthread_use_mm

Some architectures like arm64 and s390 require USER_DS to be set for kernel threads to access user address space, which is the whole purpose of kthread_use_mm, but other like x86 don't. That has lead to a huge mess where some callers are fixed up once they are tested on said architectures, while

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/gt: Free request pool from virtual engines

== Series Details == Series: drm/i915/gt: Free request pool from virtual engines URL : https://patchwork.freedesktop.org/series/75483/ State : success == Summary == CI Bug Log - changes from CI_DRM_8251_full -> Patchwork_17207_full Summary

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

Hi Namhyung, On 04.04.2020 5:18, Namhyung Kim wrote: > Hello, > > On Thu, Apr 2, 2020 at 5:47 PM Alexey Budankov > wrote: >> >> >> Extend error messages to mention CAP_PERFMON capability as an option >> to substitute CAP_SYS_ADMIN capability for secure system performance >> monitoring and

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/selftests: Wait until we start timeslicing after a submit

== Series Details == Series: drm/i915/selftests: Wait until we start timeslicing after a submit URL : https://patchwork.freedesktop.org/series/75479/ State : success == Summary == CI Bug Log - changes from CI_DRM_8251_full -> Patchwork_17206_full

Re: [Intel-gfx] [PATCH v2 5/5] uaccess: Rename user_access_begin/end() to user_full_access_begin/end()

-end/20200404-080555 base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 5364abc57993b3bf60c41923cb98a8f1a594e749 config: i386-allyesconfig (attached as .config) compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0 reproduce: # save the attached .config to linux build tree

Re: [Intel-gfx] [PATCH v2 5/5] uaccess: Rename user_access_begin/end() to user_full_access_begin/end()

-end/20200404-080555 base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 5364abc57993b3bf60c41923cb98a8f1a594e749 config: x86_64-randconfig-s1-20200404 (attached as .config) compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0 reproduce: # save the attached .config to linux