From: Sagar Arun Kamble <sagar.a.kamble@intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 03/15] drm/i915/guc: Move GuC notification handling to separate function
Date: Mon, 5 Mar 2018 13:10:19 +0530 [thread overview]
Message-ID: <da69ea5b-188a-e608-f7b1-7738aeb439a1@intel.com> (raw)
In-Reply-To: <20180227125230.13000-3-michal.winiarski@intel.com>
On 2/27/2018 6:22 PM, Michał Winiarski wrote:
> From: Michal Wajdeczko <michal.wajdeczko@intel.com>
>
> To allow future code reuse. While here, fix comment style.
>
> Suggested-by: Oscar Mateo <oscar.mateo@intel.com>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Oscar Mateo <oscar.mateo@intel.com>
> Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> ---
> drivers/gpu/drm/i915/i915_irq.c | 33 ++-------------------------------
> drivers/gpu/drm/i915/intel_guc.c | 37 +++++++++++++++++++++++++++++++++++++
> drivers/gpu/drm/i915/intel_guc.h | 1 +
> 3 files changed, 40 insertions(+), 31 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index 0a7ed990a8d1..023ba897e991 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -1759,37 +1759,8 @@ static void gen6_rps_irq_handler(struct drm_i915_private *dev_priv, u32 pm_iir)
>
> static void gen9_guc_irq_handler(struct drm_i915_private *dev_priv, u32 gt_iir)
> {
> - if (gt_iir & GEN9_GUC_TO_HOST_INT_EVENT) {
> - /* Sample the log buffer flush related bits & clear them out now
> - * itself from the message identity register to minimize the
> - * probability of losing a flush interrupt, when there are back
> - * to back flush interrupts.
> - * There can be a new flush interrupt, for different log buffer
> - * type (like for ISR), whilst Host is handling one (for DPC).
> - * Since same bit is used in message register for ISR & DPC, it
> - * could happen that GuC sets the bit for 2nd interrupt but Host
> - * clears out the bit on handling the 1st interrupt.
> - */
> - u32 msg, flush;
> -
> - msg = I915_READ(SOFT_SCRATCH(15));
> - flush = msg & (INTEL_GUC_RECV_MSG_CRASH_DUMP_POSTED |
> - INTEL_GUC_RECV_MSG_FLUSH_LOG_BUFFER);
> - if (flush) {
> - /* Clear the message bits that are handled */
> - I915_WRITE(SOFT_SCRATCH(15), msg & ~flush);
> -
> - /* Handle flush interrupt in bottom half */
> - queue_work(dev_priv->guc.log.runtime.flush_wq,
> - &dev_priv->guc.log.runtime.flush_work);
> -
> - dev_priv->guc.log.flush_interrupt_count++;
> - } else {
> - /* Not clearing of unhandled event bits won't result in
> - * re-triggering of the interrupt.
> - */
> - }
> - }
> + if (gt_iir & GEN9_GUC_TO_HOST_INT_EVENT)
> + intel_guc_notification_handler(&dev_priv->guc);
There is GUC_NOTIFICATION_EVENT (which seems to be unused though) event
whose name matches with proposed function name to some extent.
I think we should change the name to "intel_guc_g2h_int_handler" or
some other. Other events too are kind of notification to host.
Otherwise change looks good.
> }
>
> static void i9xx_pipestat_irq_reset(struct drm_i915_private *dev_priv)
> diff --git a/drivers/gpu/drm/i915/intel_guc.c b/drivers/gpu/drm/i915/intel_guc.c
> index 21140ccd7a97..f622dd6009b6 100644
> --- a/drivers/gpu/drm/i915/intel_guc.c
> +++ b/drivers/gpu/drm/i915/intel_guc.c
> @@ -364,6 +364,43 @@ int intel_guc_send_mmio(struct intel_guc *guc, const u32 *action, u32 len)
> return ret;
> }
>
> +void intel_guc_notification_handler(struct intel_guc *guc)
> +{
> + struct drm_i915_private *dev_priv = guc_to_i915(guc);
> + u32 msg, flush;
> +
> + /*
> + * Sample the log buffer flush related bits & clear them out now
> + * itself from the message identity register to minimize the
> + * probability of losing a flush interrupt, when there are back
> + * to back flush interrupts.
> + * There can be a new flush interrupt, for different log buffer
> + * type (like for ISR), whilst Host is handling one (for DPC).
> + * Since same bit is used in message register for ISR & DPC, it
> + * could happen that GuC sets the bit for 2nd interrupt but Host
> + * clears out the bit on handling the 1st interrupt.
> + */
> +
> + msg = I915_READ(SOFT_SCRATCH(15));
> + flush = msg & (INTEL_GUC_RECV_MSG_CRASH_DUMP_POSTED |
> + INTEL_GUC_RECV_MSG_FLUSH_LOG_BUFFER);
> + if (flush) {
> + /* Clear the message bits that are handled */
> + I915_WRITE(SOFT_SCRATCH(15), msg & ~flush);
> +
> + /* Handle flush interrupt in bottom half */
> + queue_work(guc->log.runtime.flush_wq,
> + &guc->log.runtime.flush_work);
> +
> + guc->log.flush_interrupt_count++;
> + } else {
> + /*
> + * Not clearing of unhandled event bits won't result in
> + * re-triggering of the interrupt.
> + */
> + }
> +}
> +
> int intel_guc_sample_forcewake(struct intel_guc *guc)
> {
> struct drm_i915_private *dev_priv = guc_to_i915(guc);
> diff --git a/drivers/gpu/drm/i915/intel_guc.h b/drivers/gpu/drm/i915/intel_guc.h
> index 52856a97477d..5b905bae181d 100644
> --- a/drivers/gpu/drm/i915/intel_guc.h
> +++ b/drivers/gpu/drm/i915/intel_guc.h
> @@ -125,6 +125,7 @@ int intel_guc_init(struct intel_guc *guc);
> void intel_guc_fini(struct intel_guc *guc);
> int intel_guc_send_nop(struct intel_guc *guc, const u32 *action, u32 len);
> int intel_guc_send_mmio(struct intel_guc *guc, const u32 *action, u32 len);
> +void intel_guc_notification_handler(struct intel_guc *guc);
> int intel_guc_sample_forcewake(struct intel_guc *guc);
> int intel_guc_auth_huc(struct intel_guc *guc, u32 rsa_offset);
> int intel_guc_suspend(struct drm_i915_private *dev_priv);
--
Thanks,
Sagar
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-05 7:40 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 12:52 [PATCH 01/15] drm/i915/guc: Tidy guc_log_control Michał Winiarski
2018-02-27 12:52 ` [PATCH 02/15] drm/i915/guc: Create common entry points for log register/unregister Michał Winiarski
2018-02-27 14:11 ` Michal Wajdeczko
2018-03-05 7:09 ` Sagar Arun Kamble
2018-03-05 13:38 ` Michał Winiarski
2018-03-06 5:24 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 03/15] drm/i915/guc: Move GuC notification handling to separate function Michał Winiarski
2018-03-05 7:40 ` Sagar Arun Kamble [this message]
2018-02-27 12:52 ` [PATCH 04/15] drm/i915/guc: Keep GuC interrupts enabled when using GuC Michał Winiarski
2018-03-05 9:27 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 05/15] drm/i915/guc: Log runtime should consist of both mapping and relay Michał Winiarski
2018-02-27 14:21 ` Michal Wajdeczko
2018-03-05 10:31 ` Sagar Arun Kamble
2018-03-05 14:14 ` Michał Winiarski
2018-03-06 5:54 ` Sagar Arun Kamble
2018-03-06 13:50 ` Chris Wilson
2018-02-27 12:52 ` [PATCH 06/15] drm/i915/guc: Merge log relay file and channel creation Michał Winiarski
2018-03-05 11:44 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 07/15] drm/i915/guc: Flush directly in log unregister Michał Winiarski
2018-03-05 11:58 ` Sagar Arun Kamble
2018-03-05 12:10 ` Michał Winiarski
2018-03-06 4:59 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 08/15] drm/i915/guc: Split relay control and GuC log level Michał Winiarski
2018-03-06 7:16 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 09/15] drm/i915/guc: Move check for fast memcpy_wc to relay creation Michał Winiarski
2018-02-27 14:37 ` Michal Wajdeczko
2018-02-27 15:37 ` Michał Winiarski
2018-03-06 14:00 ` Chris Wilson
2018-03-06 7:23 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 10/15] drm/i915/guc: Get rid of GuC log runtime Michał Winiarski
2018-03-06 9:30 ` Sagar Arun Kamble
2018-03-06 14:02 ` Chris Wilson
2018-02-27 12:52 ` [PATCH 11/15] drm/i915/guc: Always print log stats in i915_guc_info when using GuC Michał Winiarski
2018-03-06 7:41 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 12/15] drm/i915/guc: Don't print out relay statistics when relay is disabled Michał Winiarski
2018-03-06 11:21 ` Sagar Arun Kamble
2018-03-06 12:00 ` Michał Winiarski
2018-03-06 13:16 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 13/15] drm/i915/guc: Allow user to control default GuC logging Michał Winiarski
2018-03-06 11:58 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 14/15] drm/i915/guc: Default to non-verbose " Michał Winiarski
2018-03-06 13:44 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 15/15] HAX enable guc and guc_log for CI Michał Winiarski
2018-02-27 13:38 ` ✗ Fi.CI.SPARSE: warning for series starting with [01/15] drm/i915/guc: Tidy guc_log_control Patchwork
2018-02-27 13:47 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-27 13:49 ` [PATCH 01/15] " Michal Wajdeczko
2018-02-27 20:10 ` ✗ Fi.CI.IGT: failure for series starting with [01/15] " Patchwork
2018-03-02 11:09 ` [PATCH 01/15] " Sagar Arun Kamble
2018-03-02 11:52 ` Michał Winiarski
2018-03-05 5:29 ` Sagar Arun Kamble
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=da69ea5b-188a-e608-f7b1-7738aeb439a1@intel.com \
--to=sagar.a.kamble@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.winiarski@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