All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: hang.yuan@linux.intel.com
Cc: intel-gvt-dev@lists.freedesktop.org, stable@vger.kernel.org,
	Xiong Zhang <xiong.y.zhang@intel.com>
Subject: Re: [PATCH] drm/i915/gvt: move intel_runtime_pm_get out of spin_lock in stop_schedule
Date: Tue, 31 Jul 2018 17:09:22 +0200	[thread overview]
Message-ID: <20180731150922.GA13018@kroah.com> (raw)
In-Reply-To: <1533031546-29178-1-git-send-email-hang.yuan@linux.intel.com>

On Tue, Jul 31, 2018 at 06:05:46PM +0800, hang.yuan@linux.intel.com wrote:
> From: Hang Yuan <hang.yuan@linux.intel.com>
> 
> pm_runtime_get_sync in intel_runtime_pm_get might sleep if i915
> device is not active. When stop vgpu schedule, the device may be
> inactive. So need to move runtime_pm_get out of spin_lock/unlock.
> 
> Fixes: b24881e0b0b6("drm/i915/gvt: Add runtime_pm_get/put into gvt_switch_mmio
> Signed-off-by: Hang Yuan <hang.yuan@linux.intel.com>
> Signed-off-by: Xiong Zhang <xiong.y.zhang@intel.com>
> ---
>  drivers/gpu/drm/i915/gvt/mmio_context.c | 2 --
>  drivers/gpu/drm/i915/gvt/sched_policy.c | 3 +++
>  2 files changed, 3 insertions(+), 2 deletions(-)

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

  reply	other threads:[~2018-07-31 16:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 10:05 [PATCH] drm/i915/gvt: move intel_runtime_pm_get out of spin_lock in stop_schedule hang.yuan
2018-07-31 15:09 ` Greg KH [this message]
2018-08-01  2:12   ` Hang Yuan
  -- strict thread matches above, loose matches on Subject: below --
2018-08-29  9:07 hang.yuan

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=20180731150922.GA13018@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hang.yuan@linux.intel.com \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=stable@vger.kernel.org \
    --cc=xiong.y.zhang@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.