Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [[topic/core-for-CI]] Revert "perf/core: Avoid removing shared pmu_context on unregister"
Date: Wed, 28 Dec 2022 06:03:34 -0500	[thread overview]
Message-ID: <Y6wihpYj3NJiZ5fj@intel.com> (raw)
In-Reply-To: <20221228104712.995922-1-rodrigo.vivi@intel.com>

On Wed, Dec 28, 2022 at 05:47:12AM -0500, Rodrigo Vivi wrote:
> There's a complete rewrite of the core context handling in
> v6.2-rc1. find_pmu_context function used in this commit doesn't
> exist anymore. Also, let's first trust the upstream component,
> then work with them to get the issue solved if still present,
> re-introduce this patch with the old function only if extremely
> needed.

This revert was an FYI only, since I have removed this patch
directly to get drm-tip compiling again.

> 
> This reverts commit 87b32477e514aa9030a405b168581ee11910ea83.
> ---
>  kernel/events/core.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 930c99e4d89a..c3762a371dc6 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -11528,8 +11528,7 @@ void perf_pmu_unregister(struct pmu *pmu)
>  		device_del(pmu->dev);
>  		put_device(pmu->dev);
>  	}
> -	if (!find_pmu_context(pmu->task_ctx_nr))
> -		free_pmu_context(pmu);
> +	free_pmu_context(pmu);
>  	mutex_unlock(&pmus_lock);
>  }
>  EXPORT_SYMBOL_GPL(perf_pmu_unregister);
> -- 
> 2.38.1
> 

  reply	other threads:[~2022-12-28 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28 10:47 [Intel-gfx] [[topic/core-for-CI]] Revert "perf/core: Avoid removing shared pmu_context on unregister" Rodrigo Vivi
2022-12-28 11:03 ` Rodrigo Vivi [this message]
2022-12-28 11:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for ] " Patchwork
2022-12-28 12:07 ` [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=Y6wihpYj3NJiZ5fj@intel.com \
    --to=rodrigo.vivi@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