Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Animesh Manna <animesh.manna@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dsb: modified to drm_info in dsb_prepare()
Date: Thu, 24 Mar 2022 10:08:39 +0100	[thread overview]
Message-ID: <176fa37d-3c9a-15ee-bb5d-b75c33d2e498@linux.intel.com> (raw)
In-Reply-To: <20220324074300.21294-1-animesh.manna@intel.com>


On 3/24/2022 8:43 AM, Animesh Manna wrote:
> The request to aqquire gem resources is failing for DSB in rare
> scenario where it is busy and the register programming will be done
> through mmio fallback path.
>
> DSB has extra advantage of faster register programming which may
> go away through mmio path. Adding wait for gem resource also may
> not be right as anyways losing time.
>
> To make the CI execution happy replaced drm_dbg_kms() to drm_info()
> for printing debuf info during dsb buffer preparation.
>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
>   drivers/gpu/drm/i915/display/intel_dsb.c | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dsb.c b/drivers/gpu/drm/i915/display/intel_dsb.c
> index b34a67309976..b68dd7bd5271 100644
> --- a/drivers/gpu/drm/i915/display/intel_dsb.c
> +++ b/drivers/gpu/drm/i915/display/intel_dsb.c
> @@ -275,7 +275,7 @@ void intel_dsb_prepare(struct intel_crtc_state *crtc_state)
>   
>   	dsb = kmalloc(sizeof(*dsb), GFP_KERNEL);
>   	if (!dsb) {
> -		drm_err(&i915->drm, "DSB object creation failed\n");
> +		drm_info(&i915->drm, "DSB object creation failed\n");
>   		return;
>   	}
>   
> @@ -283,14 +283,14 @@ void intel_dsb_prepare(struct intel_crtc_state *crtc_state)
>   
>   	obj = i915_gem_object_create_internal(i915, DSB_BUF_SIZE);
>   	if (IS_ERR(obj)) {
> -		drm_err(&i915->drm, "Gem object creation failed\n");
> +		drm_info(&i915->drm, "Gem object creation failed\n");

If CI is happy with drm_warn then it makes sense to use drm_warn.


>   		kfree(dsb);
>   		goto out;
>   	}
>   
>   	vma = i915_gem_object_ggtt_pin(obj, NULL, 0, 0, 0);
>   	if (IS_ERR(vma)) {
> -		drm_err(&i915->drm, "Vma creation failed\n");
> +		drm_info(&i915->drm, "Vma creation failed\n");


These messages are bit vague, add "DSB VMA creation failed" or something 
similar.

With that Acked-by: Nirmoy Das <nirmoy.das@intel.com>


Nirmoy


>   		i915_gem_object_put(obj);
>   		kfree(dsb);
>   		goto out;
> @@ -298,7 +298,7 @@ void intel_dsb_prepare(struct intel_crtc_state *crtc_state)
>   
>   	buf = i915_gem_object_pin_map_unlocked(vma->obj, I915_MAP_WC);
>   	if (IS_ERR(buf)) {
> -		drm_err(&i915->drm, "Command buffer creation failed\n");
> +		drm_info(&i915->drm, "Command buffer creation failed\n");
>   		i915_vma_unpin_and_release(&vma, I915_VMA_RELEASE_MAP);
>   		kfree(dsb);
>   		goto out;

  parent reply	other threads:[~2022-03-24  9:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24  7:43 [Intel-gfx] [PATCH] drm/i915/dsb: modified to drm_info in dsb_prepare() Animesh Manna
2022-03-24  8:49 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-03-24  8:53 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-24  9:08 ` Das, Nirmoy [this message]
2022-03-25 13:22   ` [Intel-gfx] [PATCH] " Manna, Animesh
2022-03-25 13:39     ` Das, Nirmoy
2022-03-24  9:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-03-24 11:47 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2022-03-25 14:28 [Intel-gfx] [PATCH] " Animesh Manna
2022-03-25 14:58 ` Das, Nirmoy
2022-03-25 16:11 Animesh Manna
2022-04-05 11:44 ` Shankar, Uma

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=176fa37d-3c9a-15ee-bb5d-b75c33d2e498@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=animesh.manna@intel.com \
    --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