mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Changwoo Min <changwoo@igalia.com>
To: tj@kernel.org, void@manifault.com, arighi@nvidia.com
Cc: kernel-dev@igalia.com, linux-kernel@vger.kernel.org,
	Changwoo Min <changwoo@igalia.com>
Subject: [PATCH v3 0/2] sched_ext: Add trace point to sched_ext core events
Date: Tue,  4 Mar 2025 10:27:38 +0900	[thread overview]
Message-ID: <20250304012740.35473-1-changwoo@igalia.com> (raw)

Add tracing support to track sched_ext core events (/sched_ext/sched_ext_event)
to debug and monitor sched_ext schedulers. Also, change the core event type
from u64 to s64 to support negative event values.

ChangeLog v2 -> v3:
 - Change the type of @delta from __u64 to __s64 and make corresponding changes
   in scx_event_stats and scx_qmap.bpf.c.

ChangeLog v1 -> v2:
 - Rename @added field to @delta for clarity.
 - Rename sched_ext_add_event to sched_ext_event.
 - Drop the @offset field to avoid the potential misuse of non-portable numbers.

Changwoo Min (2):
  sched_ext: Change the event type from u64 to s64
  sched_ext: Add trace point to track sched_ext core events

 include/trace/events/sched_ext.h | 19 +++++++++++++++++++
 kernel/sched/ext.c               | 22 ++++++++++++----------
 tools/sched_ext/scx_qmap.bpf.c   | 16 ++++++++--------
 3 files changed, 39 insertions(+), 18 deletions(-)

-- 
2.48.1


             reply	other threads:[~2025-03-04  1:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04  1:27 Changwoo Min [this message]
2025-03-04  1:27 ` [PATCH v3 1/2] sched_ext: Change the event type from u64 to s64 Changwoo Min
2025-03-04  1:27 ` [PATCH v3 2/2] sched_ext: Add trace point to track sched_ext core events Changwoo Min
2025-03-04  6:41   ` Andrea Righi
2025-03-04 10:39     ` Changwoo Min

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=20250304012740.35473-1-changwoo@igalia.com \
    --to=changwoo@igalia.com \
    --cc=arighi@nvidia.com \
    --cc=kernel-dev@igalia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=void@manifault.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

all inboxes | Powered by JetHome®