Re: [Intel-gfx] [PATCH hmm v2 1/5] mm/hmm: make CONFIG_DEVICE_PRIVATE into a select

On Fri, 1 May 2020 15:20:44 -0300 Jason Gunthorpe wrote: > From: Jason Gunthorpe > > There is no reason for a user to select this or not directly - it should > be selected by drivers that are going to use the feature, similar to how > CONFIG_HMM_MIRROR works. > > Currently all drivers provide

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Watch out for idling during i915_gem_evict_something

== Series Details == Series: drm/i915: Watch out for idling during i915_gem_evict_something URL : https://patchwork.freedesktop.org/series/77104/ State : success == Summary == CI Bug Log - changes from CI_DRM_8456_full -> Patchwork_17617_full ===

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Replace the hardcoded I915_FENCE_TIMEOUT

== Series Details == Series: drm/i915: Replace the hardcoded I915_FENCE_TIMEOUT URL : https://patchwork.freedesktop.org/series/77103/ State : success == Summary == CI Bug Log - changes from CI_DRM_8456_full -> Patchwork_17616_full Summary -

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/gt: Couple up old virtual breadcrumb on new sibling

== Series Details == Series: drm/i915/gt: Couple up old virtual breadcrumb on new sibling URL : https://patchwork.freedesktop.org/series/77101/ State : success == Summary == CI Bug Log - changes from CI_DRM_8456_full -> Patchwork_17615_full

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/gt: Mark up the racy read of execlists->context_tag

== Series Details == Series: drm/i915/gt: Mark up the racy read of execlists->context_tag URL : https://patchwork.freedesktop.org/series/77099/ State : success == Summary == CI Bug Log - changes from CI_DRM_8456_full -> Patchwork_17614_full

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Watch out for idling during i915_gem_evict_something

== Series Details == Series: drm/i915: Watch out for idling during i915_gem_evict_something URL : https://patchwork.freedesktop.org/series/77104/ State : success == Summary == CI Bug Log - changes from CI_DRM_8456 -> Patchwork_17617 Summary

Re: [Intel-gfx] [PATCH] drm/i915: Watch out for idling during i915_gem_evict_something

Quoting Chris Wilson (2020-05-09 12:52:17) > i915_gem_evict_something() is charged with finding a slot within the GTT > that we may reuse. Since our goal is not to stall, we first look for a > slot that only overlaps idle vma. To this end, on the first pass we move > any active vma to the end of th

[Intel-gfx] [PATCH] drm/i915: Watch out for idling during i915_gem_evict_something

i915_gem_evict_something() is charged with finding a slot within the GTT that we may reuse. Since our goal is not to stall, we first look for a slot that only overlaps idle vma. To this end, on the first pass we move any active vma to the end of the search list. However, we only stopped moving acti

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Replace the hardcoded I915_FENCE_TIMEOUT

== Series Details == Series: drm/i915: Replace the hardcoded I915_FENCE_TIMEOUT URL : https://patchwork.freedesktop.org/series/77103/ State : success == Summary == CI Bug Log - changes from CI_DRM_8456 -> Patchwork_17616 Summary ---

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Replace the hardcoded I915_FENCE_TIMEOUT

== Series Details == Series: drm/i915: Replace the hardcoded I915_FENCE_TIMEOUT URL : https://patchwork.freedesktop.org/series/77103/ State : warning == Summary == $ dim checkpatch origin/drm-tip 74d6c4c5f71b drm/i915: Replace the hardcoded I915_FENCE_TIMEOUT -:112: WARNING:FILE_PATH_CHANGES:

[Intel-gfx] [CI] drm/i915: Replace the hardcoded I915_FENCE_TIMEOUT

Expose the hardcoded timeout for unsignaled foreign fences as a Kconfig option, primarily to allow brave systems to disable the timeout and solely rely on correct signaling. Signed-off-by: Chris Wilson Cc: Joonas Lahtinen Acked-by: Michael J. Ruhl --- drivers/gpu/drm/i915/Kconfig.profile

Re: [Intel-gfx] [PATCH 12/15] drm/i915: Replace the hardcoded I915_FENCE_TIMEOUT

Quoting Ruhl, Michael J (2020-05-08 14:54:50) > >-Original Message- > >From: Chris Wilson > >Sent: Thursday, May 7, 2020 9:57 AM > >To: Ruhl, Michael J ; intel- > >g...@lists.freedesktop.org > >Subject: Re: [Intel-gfx] [PATCH 12/15] drm/i915: Replace the hardcoded > >I915_FENCE_TIMEOUT > >

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: Couple up old virtual breadcrumb on new sibling

== Series Details == Series: drm/i915/gt: Couple up old virtual breadcrumb on new sibling URL : https://patchwork.freedesktop.org/series/77101/ State : success == Summary == CI Bug Log - changes from CI_DRM_8456 -> Patchwork_17615 Summary -

Re: [Intel-gfx] [PATCH] drm: Fix page flip ioctl format check

On Fri, May 8, 2020 at 7:09 PM Rodrigo Vivi wrote: > > On Fri, Apr 17, 2020 at 09:28:34PM +0300, Ville Syrjälä wrote: > > On Fri, Apr 17, 2020 at 08:10:26PM +0200, Daniel Vetter wrote: > > > On Fri, Apr 17, 2020 at 5:43 PM Ville Syrjälä > > > wrote: > > > > > > > > On Fri, Apr 17, 2020 at 05:23:1

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: Mark up the racy read of execlists->context_tag

== Series Details == Series: drm/i915/gt: Mark up the racy read of execlists->context_tag URL : https://patchwork.freedesktop.org/series/77099/ State : success == Summary == CI Bug Log - changes from CI_DRM_8456 -> Patchwork_17614 Summary -

[Intel-gfx] [PATCH] drm/i915/gt: Couple up old virtual breadcrumb on new sibling

The second try at staging the transfer of the breadcrumb. In part one, we realised we could not simply move to the second engine as we were only holding the breadcrumb lock on the first. So in commit 6c81e21a4742 ("drm/i915/gt: Stage the transfer of the virtual breadcrumb"), we removed it from the

[Intel-gfx] [PATCH] drm/i915/gt: Mark up the racy read of execlists->context_tag

Since we are using bitops on context_tag to allow us to reserve and release inflight tags concurrently, the scan for the next bit is intentionally racy. [ 516.446854] BUG: KCSAN: data-race in execlists_schedule_in.isra.0 [i915] / execlists_schedule_out [i915] [ 516.446874] [ 516.446886] write