From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Sagar Arun Kamble <sagar.a.kamble@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 06/11] drm/i915/guc: Only release GuC log object during submission_fini
Date: Wed, 18 Oct 2017 14:12:38 +0100 [thread overview]
Message-ID: <284b341c-33d6-10f6-675a-ddc7477118c7@linux.intel.com> (raw)
In-Reply-To: <1508309222-26406-7-git-send-email-sagar.a.kamble@intel.com>
On 18/10/2017 07:46, Sagar Arun Kamble wrote:
> GuC log runtime/relay channel data is released during i915 unregister,
> So only GuC log vma needs to be released during submission_fini.
>
> Signed-off-by: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_guc_submission.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_guc_submission.c b/drivers/gpu/drm/i915/i915_guc_submission.c
> index a2e8114..c360b37 100644
> --- a/drivers/gpu/drm/i915/i915_guc_submission.c
> +++ b/drivers/gpu/drm/i915/i915_guc_submission.c
> @@ -1021,7 +1021,7 @@ void i915_guc_submission_fini(struct drm_i915_private *dev_priv)
>
> ida_destroy(&guc->stage_ids);
> guc_ads_destroy(guc);
> - intel_guc_log_destroy(guc);
> + i915_vma_unpin_and_release(&guc->log.vma);
> i915_gem_object_unpin_map(guc->stage_desc_pool->obj);
> i915_vma_unpin_and_release(&guc->stage_desc_pool);
> }
>
Doesn't it make more sense to hide the logging implementation details
from this call site?
And I can't find the remaining caller of the intel_guc_log_destroy in
the current codebase? Unless it was added in one of the previous patches?
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:[~2017-10-18 13:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 6:46 [PATCH 00/11] GuC Interrupts/Log updates Sagar Arun Kamble
2017-10-18 6:46 ` [PATCH 01/11] drm/i915: Export low level PM IRQ functions to control from GuC functions Sagar Arun Kamble
2017-10-18 12:42 ` Tvrtko Ursulin
2017-10-18 13:48 ` Sagar Arun Kamble
2017-10-18 6:46 ` [PATCH 02/11] drm/i915/guc: Move GuC interrupts related functions from i915_irq.c to intel_guc.c Sagar Arun Kamble
2017-10-18 12:46 ` Tvrtko Ursulin
2017-10-18 14:06 ` Sagar Arun Kamble
2017-10-18 6:46 ` [PATCH 03/11] drm/i915/guc: Pass intel_guc struct parameter to GuC interrupts functions Sagar Arun Kamble
2017-10-18 12:47 ` Tvrtko Ursulin
2017-10-18 6:46 ` [PATCH 04/11] drm/i915/guc: Sanitize module parameter guc_log_level Sagar Arun Kamble
2017-10-18 12:59 ` Tvrtko Ursulin
2017-10-18 15:50 ` Sagar Arun Kamble
2017-10-19 7:22 ` Tvrtko Ursulin
2017-10-21 8:11 ` Sagar Arun Kamble
2017-10-18 6:46 ` [PATCH 05/11] drm/i915/guc: Make GuC log related functions depend only on log level Sagar Arun Kamble
2017-10-18 13:07 ` Tvrtko Ursulin
2017-10-18 15:57 ` Sagar Arun Kamble
2017-10-18 6:46 ` [PATCH 06/11] drm/i915/guc: Only release GuC log object during submission_fini Sagar Arun Kamble
2017-10-18 13:12 ` Tvrtko Ursulin [this message]
2017-10-18 16:04 ` Sagar Arun Kamble
2017-10-19 7:18 ` Tvrtko Ursulin
2017-10-21 8:09 ` Sagar Arun Kamble
2017-10-18 6:46 ` [PATCH 07/11] drm/i915/guc: Grab RPM wakelock while disabling GuC interrupts Sagar Arun Kamble
2017-10-19 10:09 ` Tvrtko Ursulin
2017-10-21 13:27 ` Sagar Arun Kamble
2017-10-18 6:46 ` [PATCH 08/11] drm/i915/guc: Add client support to enable/disable " Sagar Arun Kamble
2017-10-19 10:19 ` Tvrtko Ursulin
2017-10-21 16:38 ` Sagar Arun Kamble
2017-10-18 6:47 ` [PATCH 09/11] drm/i915/guc: Fix GuC interrupts disabling with Logging Sagar Arun Kamble
2017-10-19 10:24 ` Tvrtko Ursulin
2017-10-21 16:39 ` Sagar Arun Kamble
2017-10-18 6:47 ` [PATCH 10/11] drm/i915/guc: Skip interrupt enabling if logging is already enabled Sagar Arun Kamble
2017-10-19 10:31 ` Tvrtko Ursulin
2017-10-21 16:47 ` Sagar Arun Kamble
2017-10-18 6:47 ` [PATCH 11/11] drm/i915/guc: Restore GuC interrupts across suspend/reset if enabled Sagar Arun Kamble
2017-10-19 11:03 ` Tvrtko Ursulin
2017-10-21 17:09 ` Sagar Arun Kamble
2017-10-18 7:02 ` ✓ Fi.CI.BAT: success for GuC Interrupts/Log updates Patchwork
2017-10-18 13:41 ` ✓ Fi.CI.IGT: " 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=284b341c-33d6-10f6-675a-ddc7477118c7@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sagar.a.kamble@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox