All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Animesh Manna <animesh.manna@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dsb: Enable lmem for dsb
Date: Fri, 31 Jan 2020 14:03:29 +0200	[thread overview]
Message-ID: <20200131120329.GO13686@intel.com> (raw)
In-Reply-To: <20200131114258.22306-1-animesh.manna@intel.com>

On Fri, Jan 31, 2020 at 05:12:58PM +0530, Animesh Manna wrote:
> If lmem is supported DSB should use local memeory instead
> of system memory. Using local memory surely bring performance
> improvement as local memory is close to gpu. Also want to avoid
> multiple gpu using system memory.
> 
> Used LMEM api to create gem object needed for DSB command buffer.

The whole point of the dsb is to avoid doing mmio.a Now you're
replacing the nice dma with mmio again. Granted lmem is probably
wc so maybe not as slow as direct mmio register access, and also
we can do this ahead of time so not as time critical as direct
mmio during the the vblank.

> 
> v1: Initial patch.
> 
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: Ramalingam C <ramalingam.c@intel.com>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dsb.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dsb.c b/drivers/gpu/drm/i915/display/intel_dsb.c
> index 9dd18144a664..d67b6a764ba0 100644
> --- a/drivers/gpu/drm/i915/display/intel_dsb.c
> +++ b/drivers/gpu/drm/i915/display/intel_dsb.c
> @@ -6,6 +6,7 @@
>  
>  #include "i915_drv.h"
>  #include "intel_display_types.h"
> +#include "gem/i915_gem_lmem.h"
>  
>  #define DSB_BUF_SIZE    (2 * PAGE_SIZE)
>  
> @@ -113,7 +114,11 @@ intel_dsb_get(struct intel_crtc *crtc)
>  
>  	wakeref = intel_runtime_pm_get(&i915->runtime_pm);
>  
> -	obj = i915_gem_object_create_internal(i915, DSB_BUF_SIZE);
> +	if (HAS_LMEM(i915))
> +		obj = i915_gem_object_create_lmem(i915, DSB_BUF_SIZE, 0);
> +	else
> +		obj = i915_gem_object_create_internal(i915, DSB_BUF_SIZE);
> +
>  	if (IS_ERR(obj)) {
>  		DRM_ERROR("Gem object creation failed\n");
>  		goto out;
> -- 
> 2.24.0
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-01-31 12:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31 11:42 [Intel-gfx] [PATCH] drm/i915/dsb: Enable lmem for dsb Animesh Manna
2020-01-31 12:03 ` Ville Syrjälä [this message]
2020-01-31 17:24   ` Manna, Animesh
2020-01-31 14:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-01-31 15:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-03 15:55 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-02-24  9:10 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dsb: Enable lmem for dsb (rev2) Patchwork
2020-02-24 10:09 ` [Intel-gfx] ✗ Fi.CI.BAT: 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=20200131120329.GO13686@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=animesh.manna@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@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.