From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Zhi Wang <zhi.a.wang@intel.com>,
intel-gfx@lists.freedesktop.org, joonas.lahtinen@linux.intel.com,
chris@chris-wilson.co.uk, kevin.tian@intel.com,
zhiyuan.lv@intel.com
Subject: Re: [PATCH 2/9] drm/i915/gvt: Fold vGPU active check into inner functions
Date: Wed, 18 May 2016 11:54:54 +0100 [thread overview]
Message-ID: <573C49FE.1000301@linux.intel.com> (raw)
In-Reply-To: <1463473149-5876-3-git-send-email-zhi.a.wang@intel.com>
On 17/05/16 09:19, Zhi Wang wrote:
> v5:
> - Let functions take struct drm_i915_private *. (Tvrtko)
>
> - Fold vGPU related active check into the inner functions. (Kevin)
>
> Signed-off-by: Zhi Wang <zhi.a.wang@intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem_gtt.c | 11 ++++-------
> drivers/gpu/drm/i915/i915_vgpu.c | 13 +++++++++----
> drivers/gpu/drm/i915/i915_vgpu.h | 4 ++--
> 3 files changed, 15 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.c b/drivers/gpu/drm/i915/i915_gem_gtt.c
> index 7eab619..820b59e 100644
> --- a/drivers/gpu/drm/i915/i915_gem_gtt.c
> +++ b/drivers/gpu/drm/i915/i915_gem_gtt.c
> @@ -2737,11 +2737,9 @@ static int i915_gem_setup_global_gtt(struct drm_device *dev,
> i915_address_space_init(&ggtt->base, dev_priv);
> ggtt->base.total += PAGE_SIZE;
>
> - if (intel_vgpu_active(dev_priv)) {
> - ret = intel_vgt_balloon(dev);
> - if (ret)
> - return ret;
> - }
> + ret = intel_vgt_balloon(dev_priv);
> + if (ret)
> + return ret;
>
> if (!HAS_LLC(dev))
> ggtt->base.mm.color_adjust = i915_gtt_color_adjust;
> @@ -2841,8 +2839,7 @@ void i915_ggtt_cleanup_hw(struct drm_device *dev)
> i915_gem_cleanup_stolen(dev);
>
> if (drm_mm_initialized(&ggtt->base.mm)) {
> - if (intel_vgpu_active(dev_priv))
> - intel_vgt_deballoon();
> + intel_vgt_deballoon(dev_priv);
>
> drm_mm_takedown(&ggtt->base.mm);
> list_del(&ggtt->base.global_link);
> diff --git a/drivers/gpu/drm/i915/i915_vgpu.c b/drivers/gpu/drm/i915/i915_vgpu.c
> index d5a7a5e..5312816 100644
> --- a/drivers/gpu/drm/i915/i915_vgpu.c
> +++ b/drivers/gpu/drm/i915/i915_vgpu.c
> @@ -101,10 +101,13 @@ static struct _balloon_info_ bl_info;
> * This function is called to deallocate the ballooned-out graphic memory, when
> * driver is unloaded or when ballooning fails.
> */
> -void intel_vgt_deballoon(void)
> +void intel_vgt_deballoon(struct drm_i915_private *dev_priv)
> {
> int i;
>
> + if (!intel_vgpu_active(dev_priv))
> + return;
> +
> DRM_DEBUG("VGT deballoon.\n");
>
> for (i = 0; i < 4; i++) {
> @@ -177,9 +180,8 @@ static int vgt_balloon_space(struct drm_mm *mm,
> * Returns:
> * zero on success, non-zero if configuration invalid or ballooning failed
> */
> -int intel_vgt_balloon(struct drm_device *dev)
> +int intel_vgt_balloon(struct drm_i915_private *dev_priv)
> {
> - struct drm_i915_private *dev_priv = to_i915(dev);
> struct i915_ggtt *ggtt = &dev_priv->ggtt;
> unsigned long ggtt_end = ggtt->base.start + ggtt->base.total;
>
> @@ -187,6 +189,9 @@ int intel_vgt_balloon(struct drm_device *dev)
> unsigned long unmappable_base, unmappable_size, unmappable_end;
> int ret;
>
> + if (!intel_vgpu_active(dev_priv))
> + return 0;
> +
> mappable_base = I915_READ(vgtif_reg(avail_rs.mappable_gmadr.base));
> mappable_size = I915_READ(vgtif_reg(avail_rs.mappable_gmadr.size));
> unmappable_base = I915_READ(vgtif_reg(avail_rs.nonmappable_gmadr.base));
> @@ -258,6 +263,6 @@ int intel_vgt_balloon(struct drm_device *dev)
>
> err:
> DRM_ERROR("VGT balloon fail\n");
> - intel_vgt_deballoon();
> + intel_vgt_deballoon(dev_priv);
> return ret;
> }
> diff --git a/drivers/gpu/drm/i915/i915_vgpu.h b/drivers/gpu/drm/i915/i915_vgpu.h
> index 07e67d5..f8917c6 100644
> --- a/drivers/gpu/drm/i915/i915_vgpu.h
> +++ b/drivers/gpu/drm/i915/i915_vgpu.h
> @@ -27,7 +27,7 @@
> #include "i915_pvinfo.h"
>
> extern void i915_check_vgpu(struct drm_i915_private *dev_priv);
> -extern int intel_vgt_balloon(struct drm_device *dev);
> -extern void intel_vgt_deballoon(void);
> +extern int intel_vgt_balloon(struct drm_i915_private *dev_priv);
> +extern void intel_vgt_deballoon(struct drm_i915_private *dev_priv);
>
> #endif /* _I915_VGPU_H_ */
>
Looks clean to me.
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-18 10:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 8:19 [PATCH 0/9] Introduce the implementation of GVT context Zhi Wang
2016-05-17 8:19 ` [PATCH 1/9] drm/i915: Factor out i915_pvinfo.h Zhi Wang
2016-05-17 8:19 ` [PATCH 2/9] drm/i915/gvt: Fold vGPU active check into inner functions Zhi Wang
2016-05-18 10:54 ` Tvrtko Ursulin [this message]
2016-05-20 10:27 ` Wang, Zhi A
2016-05-17 8:19 ` [PATCH 3/9] drm/i915: gvt: Introduce the basic architecture of GVT-g Zhi Wang
2016-05-18 11:22 ` Tvrtko Ursulin
2016-05-20 10:57 ` Wang, Zhi A
2016-05-20 11:49 ` Chris Wilson
2016-05-20 12:18 ` Wang, Zhi A
2016-05-20 12:37 ` Chris Wilson
2016-05-17 8:19 ` [PATCH 4/9] drm/i915: Introduce host graphics memory partition for GVT-g Zhi Wang
2016-05-20 12:00 ` Chris Wilson
2016-05-20 12:19 ` Wang, Zhi A
2016-05-17 8:19 ` [PATCH 5/9] drm/i915: Make ring buffer size configurable Zhi Wang
2016-05-20 12:01 ` Chris Wilson
2016-05-20 12:20 ` Wang, Zhi A
2016-05-17 8:19 ` [PATCH 6/9] drm/i915: Generate addressing mode bit from flag in context Zhi Wang
2016-05-20 12:03 ` Chris Wilson
2016-05-20 12:23 ` Wang, Zhi A
2016-05-17 8:19 ` [PATCH 7/9] drm/i915: Introduce execlist context status change notification Zhi Wang
2016-05-17 10:51 ` Tvrtko Ursulin
2016-05-17 15:18 ` Wang, Zhi A
2016-05-20 11:16 ` Chris Wilson
2016-05-20 11:42 ` Wang, Zhi A
2016-05-17 8:19 ` [PATCH 8/9] drm/i915: Support context single submission Zhi Wang
2016-05-20 12:04 ` Chris Wilson
2016-05-17 8:19 ` [PATCH 9/9] drm/i915: Introduce GVT context creation API Zhi Wang
2016-05-20 12:06 ` Chris Wilson
2016-05-17 8:56 ` ✗ Ro.CI.BAT: failure for Introduce the implementation of GVT context (rev2) 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=573C49FE.1000301@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=zhi.a.wang@intel.com \
--cc=zhiyuan.lv@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.