From: Qais Yousef <qais.yousef@arm.com>
To: "Peter Zijlstra (Intel)" <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Steven Rostedt <rostedt@goodmis.org>,
Phil Auld <pauld@redhat.com>,
Giovanni Gherdovich <ggherdovich@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Remove sched_trace_*() helper functions
Date: Fri, 29 Apr 2022 09:52:13 +0100 [thread overview]
Message-ID: <20220429085213.43wytbmn32m5ohlj@wubuntu> (raw)
In-Reply-To: <20220428144338.479094-1-qais.yousef@arm.com>
+CC lkml
On 04/28/22 15:43, Qais Yousef wrote:
> This is a respin of the patches Dietmar sent a while ago
>
> https://lore.kernel.org/all/20200907091717.26116-1-dietmar.eggemann@arm.com/
>
> I moved the sched_tp module to use pahole + DWARF/BTF to get the definitions
> required so that we can maintain these helpers more easily out-of-tree within
> the module.
>
> Thanks to my colleague Douglas Raillard for helping with fixing the alignment
> issues in pahole when using BTF.
>
>
> Dietmar Eggemann (2):
> sched/fair: Remove sched_trace_*() helper functions
> sched/fair: Remove cfs_rq_tg_path()
>
> include/linux/sched.h | 14 -----
> kernel/sched/fair.c | 117 ------------------------------------------
> 2 files changed, 131 deletions(-)
>
> --
> 2.25.1
>
next parent reply other threads:[~2022-04-29 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220428144338.479094-1-qais.yousef@arm.com>
2022-04-29 8:52 ` Qais Yousef [this message]
[not found] ` <20220428144338.479094-3-qais.yousef@arm.com>
2022-04-29 8:53 ` [PATCH 2/2] sched/fair: Remove cfs_rq_tg_path() Qais Yousef
2022-04-29 20:35 ` [tip: sched/core] " tip-bot2 for Dietmar Eggemann
[not found] ` <20220428144338.479094-2-qais.yousef@arm.com>
2022-04-29 8:52 ` [PATCH 1/2] sched/fair: Remove sched_trace_*() helper functions Qais Yousef
2022-04-29 20:35 ` [tip: sched/core] " tip-bot2 for Dietmar Eggemann
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=20220429085213.43wytbmn32m5ohlj@wubuntu \
--to=qais.yousef@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=ggherdovich@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.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®