Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/pmu: Check if pmu is closed before stopping event
Date: Tue, 24 Oct 2023 14:07:05 +0200	[thread overview]
Message-ID: <ZTezaaWGMAQ6NO6M@ashyti-mobl2.lan> (raw)
In-Reply-To: <20231019182836.3761023-1-umesh.nerlige.ramappa@intel.com>

Hi Umesh,

On Thu, Oct 19, 2023 at 11:28:36AM -0700, Umesh Nerlige Ramappa wrote:
> When the driver unbinds, pmu is unregistered and i915->uabi_engines is
> set to RB_ROOT. Due to this, when i915 PMU tries to stop the engine
> events, it issues a warn_on because engine lookup fails.
> 
> All perf hooks are taking care of this using a pmu->closed flag that is
> set when PMU unregisters. The stop event seems to have been left out.
> 
> Check for pmu->closed in pmu_event_stop as well.
> 
> Based on discussion here -
> https://patchwork.freedesktop.org/patch/492079/?series=105790&rev=2
> 
> v2: s/is/if/ in commit title

Please, next time version your patches. This is the third time
you send this, but there is only one 'v2' changelog.

> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>

With Tvrtko's tags:

Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>

Andi

  parent reply	other threads:[~2023-10-24 12:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 18:28 [Intel-gfx] [PATCH] drm/i915/pmu: Check if pmu is closed before stopping event Umesh Nerlige Ramappa
2023-10-20  8:03 ` Tvrtko Ursulin
2023-10-24 12:07 ` Andi Shyti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-20 15:24 Umesh Nerlige Ramappa
2023-10-24 12:20 ` Andi Shyti
2023-10-25 19:36   ` Umesh Nerlige Ramappa
2023-10-25 11:53 ` Andi Shyti

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=ZTezaaWGMAQ6NO6M@ashyti-mobl2.lan \
    --to=andi.shyti@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=umesh.nerlige.ramappa@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