public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 22/27] drm/i915/overlay: Drop struct_mutex guard
Date: Wed, 25 Sep 2019 14:01:51 +0100	[thread overview]
Message-ID: <4ceb0514-e826-c977-93e8-66f2629aeb6b@linux.intel.com> (raw)
In-Reply-To: <156941601316.4979.6446919481910178240@skylake-alporthouse-com>


On 25/09/2019 13:53, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-09-25 13:43:46)
>>
>> On 25/09/2019 11:01, Chris Wilson wrote:
>>> The overlay uses the modeset mutex to control itself and only required
>>> the struct_mutex for requests, which is now obsolete.
>>>
>>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>> ---
>>>    drivers/gpu/drm/i915/display/intel_display.c |  7 +------
>>>    drivers/gpu/drm/i915/display/intel_overlay.c | 13 -------------
>>>    drivers/gpu/drm/i915/gt/intel_reset.c        |  4 ----
>>>    3 files changed, 1 insertion(+), 23 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
>>> index 99ddbb7bedbc..038f14d9b5c9 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_display.c
>>> +++ b/drivers/gpu/drm/i915/display/intel_display.c
>>> @@ -5738,13 +5738,8 @@ void hsw_disable_ips(const struct intel_crtc_state *crtc_state)
>>>    
>>>    static void intel_crtc_dpms_overlay_disable(struct intel_crtc *intel_crtc)
>>>    {
>>> -     if (intel_crtc->overlay) {
>>> -             struct drm_device *dev = intel_crtc->base.dev;
>>> -
>>> -             mutex_lock(&dev->struct_mutex);
>>> +     if (intel_crtc->overlay)
>>>                (void) intel_overlay_switch_off(intel_crtc->overlay);
>>> -             mutex_unlock(&dev->struct_mutex);
>>> -     }
>>>    
>>>        /* Let userspace switch the overlay on again. In most cases userspace
>>>         * has to recompute where to put it anyway.
>>> diff --git a/drivers/gpu/drm/i915/display/intel_overlay.c b/drivers/gpu/drm/i915/display/intel_overlay.c
>>> index e12e1a753af0..daea112cbb87 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_overlay.c
>>> +++ b/drivers/gpu/drm/i915/display/intel_overlay.c
>>> @@ -439,8 +439,6 @@ static int intel_overlay_release_old_vid(struct intel_overlay *overlay)
>>>        struct i915_request *rq;
>>>        u32 *cs;
>>>    
>>> -     lockdep_assert_held(&dev_priv->drm.struct_mutex);
>>> -
>>>        /*
>>>         * Only wait if there is actually an old frame to release to
>>>         * guarantee forward progress.
>>> @@ -751,7 +749,6 @@ static int intel_overlay_do_put_image(struct intel_overlay *overlay,
>>>        struct i915_vma *vma;
>>>        int ret, tmp_width;
>>>    
>>> -     lockdep_assert_held(&dev_priv->drm.struct_mutex);
>>>        WARN_ON(!drm_modeset_is_locked(&dev_priv->drm.mode_config.connection_mutex));
>>>    
>>>        ret = intel_overlay_release_old_vid(overlay);
>>> @@ -852,7 +849,6 @@ int intel_overlay_switch_off(struct intel_overlay *overlay)
>>>        struct drm_i915_private *dev_priv = overlay->i915;
>>>        int ret;
>>>    
>>> -     lockdep_assert_held(&dev_priv->drm.struct_mutex);
>>>        WARN_ON(!drm_modeset_is_locked(&dev_priv->drm.mode_config.connection_mutex));
>>>    
>>>        ret = intel_overlay_recover_from_interrupt(overlay);
>>> @@ -1068,11 +1064,7 @@ int intel_overlay_put_image_ioctl(struct drm_device *dev, void *data,
>>>    
>>>        if (!(params->flags & I915_OVERLAY_ENABLE)) {
>>>                drm_modeset_lock_all(dev);
>>> -             mutex_lock(&dev->struct_mutex);
>>> -
>>>                ret = intel_overlay_switch_off(overlay);
>>> -
>>> -             mutex_unlock(&dev->struct_mutex);
>>>                drm_modeset_unlock_all(dev);
>>>    
>>>                return ret;
>>> @@ -1088,7 +1080,6 @@ int intel_overlay_put_image_ioctl(struct drm_device *dev, void *data,
>>>                return -ENOENT;
>>>    
>>>        drm_modeset_lock_all(dev);
>>> -     mutex_lock(&dev->struct_mutex);
>>>    
>>>        if (i915_gem_object_is_tiled(new_bo)) {
>>>                DRM_DEBUG_KMS("buffer used for overlay image can not be tiled\n");
>>> @@ -1152,14 +1143,12 @@ int intel_overlay_put_image_ioctl(struct drm_device *dev, void *data,
>>>        if (ret != 0)
>>>                goto out_unlock;
>>>    
>>> -     mutex_unlock(&dev->struct_mutex);
>>>        drm_modeset_unlock_all(dev);
>>>        i915_gem_object_put(new_bo);
>>>    
>>>        return 0;
>>>    
>>>    out_unlock:
>>> -     mutex_unlock(&dev->struct_mutex);
>>>        drm_modeset_unlock_all(dev);
>>>        i915_gem_object_put(new_bo);
>>>    
>>> @@ -1233,7 +1222,6 @@ int intel_overlay_attrs_ioctl(struct drm_device *dev, void *data,
>>>        }
>>>    
>>>        drm_modeset_lock_all(dev);
>>> -     mutex_lock(&dev->struct_mutex);
>>>    
>>>        ret = -EINVAL;
>>>        if (!(attrs->flags & I915_OVERLAY_UPDATE_ATTRS)) {
>>> @@ -1290,7 +1278,6 @@ int intel_overlay_attrs_ioctl(struct drm_device *dev, void *data,
>>>    
>>>        ret = 0;
>>>    out_unlock:
>>> -     mutex_unlock(&dev->struct_mutex);
>>>        drm_modeset_unlock_all(dev);
>>>    
>>>        return ret;
>>> diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
>>> index 2685c0103e90..ee0c5c24282c 100644
>>> --- a/drivers/gpu/drm/i915/gt/intel_reset.c
>>> +++ b/drivers/gpu/drm/i915/gt/intel_reset.c
>>> @@ -1265,10 +1265,6 @@ int intel_gt_terminally_wedged(struct intel_gt *gt)
>>>        if (!test_bit(I915_RESET_BACKOFF, &gt->reset.flags))
>>>                return -EIO;
>>>    
>>> -     /* XXX intel_reset_finish() still takes struct_mutex!!! */
>>> -     if (mutex_is_locked(&gt->i915->drm.struct_mutex))
>>> -             return -EAGAIN;
>>> -
>>
>> What is this hunk doing here?
> 
> Because the overlay used struct_mutex, now it does not.

Now you see why I insist on comments and even better if they are up to 
date! :) (intel_reset_finish?!)

If you are confident overlay is the only place which can interfere here 
then:

Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

If not we'll find out sooner or later.

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-09-25 13:01 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 10:01 struct_mutex is over the hill and far away Chris Wilson
2019-09-25 10:01 ` [PATCH 01/27] dma-fence: Serialise signal enabling (dma_fence_enable_sw_signaling) Chris Wilson
2019-09-25 10:01 ` [PATCH 02/27] drm/mm: Pack allocated/scanned boolean into a bitfield Chris Wilson
2019-09-25 10:01 ` [PATCH 03/27] drm/i915: Only track bound elements of the GTT Chris Wilson
2019-09-25 10:01 ` [PATCH 04/27] drm/i915: Mark up address spaces that may need to allocate Chris Wilson
2019-09-25 10:01 ` [PATCH 05/27] drm/i915: Pull i915_vma_pin under the vm->mutex Chris Wilson
2019-09-27  8:47   ` Tvrtko Ursulin
2019-09-27 11:06     ` Chris Wilson
2019-09-25 10:01 ` [PATCH 06/27] drm/i915: Push the i915_active.retire into a worker Chris Wilson
2019-09-25 10:01 ` [PATCH 07/27] drm/i915: Coordinate i915_active with its own mutex Chris Wilson
2019-09-27 11:10   ` Tvrtko Ursulin
2019-09-27 11:25     ` Chris Wilson
2019-09-27 12:08       ` Tvrtko Ursulin
2019-09-27 12:16         ` Chris Wilson
2019-09-27 12:25           ` Tvrtko Ursulin
2019-09-27 12:32             ` Chris Wilson
2019-09-27 13:58               ` Tvrtko Ursulin
2019-09-27 14:10                 ` Chris Wilson
2019-09-25 10:01 ` [PATCH 08/27] drm/i915: Move idle barrier cleanup into engine-pm Chris Wilson
2019-09-25 10:01 ` [PATCH 09/27] drm/i915: Drop struct_mutex from around i915_retire_requests() Chris Wilson
2019-09-25 10:01 ` [PATCH 10/27] drm/i915: Remove the GEM idle worker Chris Wilson
2019-09-25 10:01 ` [PATCH 11/27] drm/i915: Merge wait_for_timelines with retire_request Chris Wilson
2019-09-25 10:47   ` Tvrtko Ursulin
2019-09-25 10:54     ` Chris Wilson
2019-09-25 10:01 ` [PATCH 12/27] drm/i915: Move request runtime management onto gt Chris Wilson
2019-09-25 10:57   ` Tvrtko Ursulin
2019-09-25 11:17     ` Chris Wilson
2019-09-25 11:24       ` Chris Wilson
2019-09-25 11:29         ` Chris Wilson
2019-09-25 11:33           ` Chris Wilson
2019-09-25 15:17             ` Tvrtko Ursulin
2019-09-25 10:01 ` [PATCH 13/27] drm/i915: Move global activity tracking from GEM to GT Chris Wilson
2019-09-25 10:01 ` [PATCH 14/27] drm/i915: Expose engine properties via sysfs Chris Wilson
2019-09-27 20:48   ` Rodrigo Vivi
2019-09-25 10:01 ` [PATCH 15/27] drm/i915/execlists: Force preemption Chris Wilson
2019-09-25 10:01 ` [PATCH 16/27] drm/i915: Mark up "sentinel" requests Chris Wilson
2019-09-25 10:01 ` [PATCH 17/27] drm/i915/execlists: Cancel banned contexts on schedule-out Chris Wilson
2019-09-25 10:01 ` [PATCH 18/27] drm/i915: Cancel non-persistent contexts on close Chris Wilson
2019-09-25 10:01 ` [PATCH 19/27] drm/i915: Replace hangcheck by heartbeats Chris Wilson
2019-09-27  8:26   ` Joonas Lahtinen
2019-09-27  9:18     ` Chris Wilson
2019-09-25 10:01 ` [PATCH 20/27] drm/i915: Remove logical HW ID Chris Wilson
2019-09-25 12:41   ` Tvrtko Ursulin
2019-09-25 12:51     ` Chris Wilson
2019-09-25 14:38       ` Tvrtko Ursulin
2019-09-25 17:59     ` Daniele Ceraolo Spurio
2019-09-25 18:23       ` Matthew Brost
2019-09-25 10:01 ` [PATCH 21/27] drm/i915: Move context management under GEM Chris Wilson
2019-09-26 13:57   ` Tvrtko Ursulin
2019-10-02 16:09     ` Tvrtko Ursulin
2019-10-03  7:35     ` Chris Wilson
2019-09-25 10:01 ` [PATCH 22/27] drm/i915/overlay: Drop struct_mutex guard Chris Wilson
2019-09-25 12:43   ` Tvrtko Ursulin
2019-09-25 12:53     ` Chris Wilson
2019-09-25 13:01       ` Tvrtko Ursulin [this message]
2019-09-25 13:11         ` Chris Wilson
2019-09-25 10:01 ` [PATCH 23/27] drm/i915: Drop struct_mutex guard from debugfs/framebuffer_info Chris Wilson
2019-09-25 12:45   ` Tvrtko Ursulin
2019-09-25 10:01 ` [PATCH 24/27] drm/i915: Remove struct_mutex guard for debugfs/opregion Chris Wilson
2019-09-25 12:51   ` Tvrtko Ursulin
2019-09-25 10:01 ` [PATCH 25/27] drm/i915: Drop struct_mutex from suspend state save/restore Chris Wilson
2019-09-25 12:52   ` Tvrtko Ursulin
2019-09-25 10:01 ` [PATCH 26/27] drm/i915/selftests: Drop vestigal struct_mutex guards Chris Wilson
2019-09-25 12:55   ` Tvrtko Ursulin
2019-09-25 10:01 ` [PATCH 27/27] drm/i915: Drop struct_mutex from around GEM initialisation Chris Wilson
2019-09-25 12:56   ` Tvrtko Ursulin
2019-09-25 10:21 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/27] dma-fence: Serialise signal enabling (dma_fence_enable_sw_signaling) Patchwork
2019-09-25 10:34 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-09-25 10:51 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-26  0:56 ` ✗ Fi.CI.IGT: failure " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ceb0514-e826-c977-93e8-66f2629aeb6b@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox