All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charlie Jenkins <charlie@rivosinc.com>
To: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Atish Patra <atishp@rivosinc.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shunsuke Nakamura <nakamura.shun@fujitsu.com>
Subject: Re: [PATCH v2 0/3] perf: Add PERF_EVENT_IOC_INC_EVENT_LIMIT
Date: Thu, 22 Aug 2024 20:40:26 -0700	[thread overview]
Message-ID: <ZsgEqrR6eux9kFcx@ghost> (raw)
In-Reply-To: <20240807-perf_set_event_limit-v2-0-823b78d04c76@rivosinc.com>

On Wed, Aug 07, 2024 at 05:02:39PM -0700, Charlie Jenkins wrote:
> Introduce a new perf ioctl key PERF_EVENT_IOC_INC_EVENT_LIMIT that
> functions the same as PERF_EVENT_IOC_REFRESH, except it does not
> immediately enable counters.
> 
> Also create a libperf API perf_evsel__refresh() to allow libperf users
> access to this ioctl key.
> 
> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
> ---
> Changes in v2:
> - Drop discussion about signal race condition
> - Add new patch "libperf: Add perf_evsel__refresh() function"
> - This newly added patch was pulled from a different series with
>   modifications to fit the new ioctl key
> -
> https://lore.kernel.org/lkml/20240726-overflow_check_libperf-v2-0-7d154dcf6bea@rivosinc.com/
> will be updated
> - Link to v1: https://lore.kernel.org/r/20240724-perf_set_event_limit-v1-0-e680c93eca55@rivosinc.com
> 
> ---
> Charlie Jenkins (3):
>       perf: Add PERF_EVENT_IOC_INC_EVENT_LIMIT
>       perf: Document PERF_EVENT_IOC_INC_EVENT_LIMIT
>       libperf: Add perf_evsel__refresh() function
> 
>  include/linux/perf_event.h               |  4 +--
>  include/uapi/linux/perf_event.h          |  1 +
>  kernel/events/core.c                     | 17 +++++++----
>  tools/include/uapi/linux/perf_event.h    |  1 +
>  tools/lib/perf/Documentation/libperf.txt |  2 ++
>  tools/lib/perf/evsel.c                   | 49 ++++++++++++++++++++++++++------
>  tools/lib/perf/include/perf/evsel.h      |  2 ++
>  tools/lib/perf/libperf.map               |  2 ++
>  tools/perf/design.txt                    |  5 ++++
>  9 files changed, 67 insertions(+), 16 deletions(-)
> ---
> base-commit: 0c3836482481200ead7b416ca80c68a29cfdaabd
> change-id: 20240724-perf_set_event_limit-079f1b996376
> -- 
> - Charlie
> 

I am interested in people's opinion of this. Let me know if there are
any concerns.

- Charlie


      parent reply	other threads:[~2024-08-23  3:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08  0:02 [PATCH v2 0/3] perf: Add PERF_EVENT_IOC_INC_EVENT_LIMIT Charlie Jenkins
2024-08-08  0:02 ` [PATCH v2 1/3] " Charlie Jenkins
2024-08-08  0:02 ` [PATCH v2 2/3] perf: Document PERF_EVENT_IOC_INC_EVENT_LIMIT Charlie Jenkins
2024-08-08  0:02 ` [PATCH v2 3/3] libperf: Add perf_evsel__refresh() function Charlie Jenkins
2024-08-23  3:40 ` Charlie Jenkins [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=ZsgEqrR6eux9kFcx@ghost \
    --to=charlie@rivosinc.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=atishp@rivosinc.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=nakamura.shun@fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.