public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	x86@kernel.org, Like Xu <likexu@tencent.com>
Subject: Re: [PATCH] x86: events: Do not return bogus capabilities if PMU is broken
Date: Wed, 1 Jun 2022 13:07:46 +0200	[thread overview]
Message-ID: <YpdIgm8c5YEFLCCH@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220601094256.362047-1-pbonzini@redhat.com>

On Wed, Jun 01, 2022 at 05:42:56AM -0400, Paolo Bonzini wrote:
> From: Like Xu <likexu@tencent.com>
> 
> If the PMU is broken due to firmware issues, check_hw_exists() will return
> false but perf_get_x86_pmu_capability() will still return data from x86_pmu.
> Likewise if some of the hotplug callbacks cannot be installed the contents
> of x86_pmu will not be reverted.
> 
> Handle the failure in both cases by clearing x86_pmu if init_hw_perf_events()
> or reverts to software events only.
> 
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

No SoB from Like,

> ---
>  arch/x86/events/core.c | 12 ++++++++++--
>  1 file changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
> index 99cf67d63cf3..d23f3821daf5 100644
> --- a/arch/x86/events/core.c
> +++ b/arch/x86/events/core.c
> @@ -2095,14 +2095,15 @@ static int __init init_hw_perf_events(void)
>  	}
>  	if (err != 0) {
>  		pr_cont("no PMU driver, software events only.\n");
> -		return 0;
> +		err = 0;
> +		goto out_bad_pmu;
>  	}
>  
>  	pmu_check_apic();
>  
>  	/* sanity check that the hardware exists or is emulated */
>  	if (!check_hw_exists(&pmu, x86_pmu.num_counters, x86_pmu.num_counters_fixed))
> -		return 0;
> +		goto out_bad_pmu;
>  
>  	pr_cont("%s PMU driver.\n", x86_pmu.name);
>  
> @@ -2211,6 +2212,8 @@ static int __init init_hw_perf_events(void)
>  	cpuhp_remove_state(CPUHP_AP_PERF_X86_STARTING);
>  out:
>  	cpuhp_remove_state(CPUHP_PERF_X86_PREPARE);
> +out_bad_pmu:
> +	memset(&x86_pmu, 0, sizeof(x86_pmu));
>  	return err;
>  }
>  early_initcall(init_hw_perf_events);
> @@ -2982,6 +2985,11 @@ unsigned long perf_misc_flags(struct pt_regs *regs)
>  
>  void perf_get_x86_pmu_capability(struct x86_pmu_capability *cap)
>  {
> +	if (!x86_pmu.name) {

We have x86_pmu_initialized(), the implementation is a bit daft, but
might as well use it here too, no?

> +		memset(cap, 0, sizeof(*cap));
> +		return;
> +	}
> +
>  	cap->version		= x86_pmu.version;
>  	/*
>  	 * KVM doesn't support the hybrid PMU yet.

Otherwise seems fine I suppose.

  reply	other threads:[~2022-06-01 11:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01  9:42 [PATCH] x86: events: Do not return bogus capabilities if PMU is broken Paolo Bonzini
2022-06-01 11:07 ` Peter Zijlstra [this message]
2022-06-01 11:24   ` Paolo Bonzini

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=YpdIgm8c5YEFLCCH@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=likexu@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=x86@kernel.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