mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	namhyung@kernel.org, irogers@google.com, adrian.hunter@intel.com,
	linux-kernel@vger.kernel.org
Cc: ak@linux.intel.com, eranian@google.com, dapeng1.mi@linux.intel.com
Subject: Re: [PATCH] perf/x86/intel/ds: Fix counter backwards of non-precise events counters-snapshotting
Date: Mon, 24 Mar 2025 13:26:23 -0400	[thread overview]
Message-ID: <d084e81c-19eb-4424-9fa9-868b75786527@linux.intel.com> (raw)
In-Reply-To: <20250204210514.4089680-1-kan.liang@linux.intel.com>

Hi Peter,

The patch is to fix a counters-snapshotting backwards issue with
non-precise events in freq mode. Could you please pick it up as well?

Thanks,
Kan

On 2025-02-04 4:05 p.m., kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
> 
> The counter backwards may be observed in the PMI handler when
> counters-snapshotting some non-precise events in the freq mode.
> 
> For the non-precise events, it's possible the counters-snapshotting
> records a positive value for an overflowed PEBS event. Then the HW
> auto-reload mechanism reset the counter to 0 immediately. Because the
> pebs_event_reset is cleared in the freq mode, which doesn't set the
> PERF_X86_EVENT_AUTO_RELOAD.
> In the PMI handler, 0 will be read rather than the positive value
> recorded in the counters-snapshotting record.
> 
> The counters-snapshotting case has to be specially handled. Since the
> event value has been updated when processing the counters-snapshotting
> record, only needs to set the new period for the counter via
> x86_pmu_set_period().
> 
> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
> ---
>  arch/x86/events/intel/ds.c | 21 +++++++++++++++++++--
>  1 file changed, 19 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/x86/events/intel/ds.c b/arch/x86/events/intel/ds.c
> index 46aaaeae0c8d..e8f808905871 100644
> --- a/arch/x86/events/intel/ds.c
> +++ b/arch/x86/events/intel/ds.c
> @@ -2377,8 +2377,25 @@ __intel_pmu_pebs_last_event(struct perf_event *event,
>  			 */
>  			intel_pmu_save_and_restart_reload(event, count);
>  		}
> -	} else
> -		intel_pmu_save_and_restart(event);
> +	} else {
> +		/*
> +		 * For a non-precise event, it's possible the
> +		 * counters-snapshotting records a positive value for the
> +		 * overflowed event. Then the HW auto-reload mechanism
> +		 * reset the counter to 0 immediately, because the
> +		 * pebs_event_reset is cleared if the PERF_X86_EVENT_AUTO_RELOAD
> +		 * is not set. The counter backwards may be observed in a
> +		 * PMI handler.
> +		 *
> +		 * Since the event value has been updated when processing the
> +		 * counters-snapshotting record, only needs to set the new
> +		 * period for the counter.
> +		 */
> +		if (is_pebs_counter_event_group(event))
> +			static_call(x86_pmu_set_period)(event);
> +		else
> +			intel_pmu_save_and_restart(event);
> +	}
>  }
>  
>  static __always_inline void


      reply	other threads:[~2025-03-24 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 21:05 kan.liang
2025-03-24 17:26 ` Liang, Kan [this message]

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=d084e81c-19eb-4424-9fa9-868b75786527@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®