All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Pat Somaru <patso@likewhatevs.io>
Cc: sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
	Emil Tsalapatis <emil@etsalapatis.com>
Subject: Re: [PATCH v2] sched_ext: Add tracepoint for scheduler exit
Date: Tue, 07 Jul 2026 12:46:17 -1000	[thread overview]
Message-ID: <2d3d31a802b30f340248db4a986cfa4c@kernel.org> (raw)
In-Reply-To: <20260707090314.2567145-1-patso@likewhatevs.io>

Hello, Pat.

Thanks, but name and level don't pin down a scheduler in a hierarchy -
same-program instances under sibling cgroups share both. Recording
sub_cgroup_id and cgrp_path too would make the events self-identifying. Both
are already on sch. Care to add them in a v3?

Thanks.

--
tejun

  reply	other threads:[~2026-07-07 22:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  5:56 [PATCH] sched_ext: Add tracepoint for scheduler exit Pat Somaru
2026-05-12 18:08 ` Tejun Heo
2026-05-13  5:08 ` sashiko-bot
2026-07-07  9:03 ` [PATCH v2] " Pat Somaru
2026-07-07 22:46   ` Tejun Heo [this message]
2026-07-10  5:59     ` [PATCH v3] " Pat Somaru
2026-07-10 16:36       ` Tejun Heo

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=2d3d31a802b30f340248db4a986cfa4c@kernel.org \
    --to=tj@kernel.org \
    --cc=emil@etsalapatis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patso@likewhatevs.io \
    --cc=sched-ext@lists.linux.dev \
    /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.