From: Shrikanth Hegde <sshegde@linux.vnet.ibm.com>
To: mingo@kernel.org, peterz@infradead.org, vincent.guittot@linaro.org
Cc: sshegde@linux.vnet.ibm.com, dietmar.eggemann@arm.com,
linux-kernel@vger.kernel.org, srikar@linux.vnet.ibm.com,
yu.c.chen@intel.com, tim.c.chen@linux.intel.com
Subject: [PATCH v2 0/2] sched: use existing helper function for accessing avg_rt, avg_dl and avg_irq
Date: Mon, 1 Jan 2024 21:16:22 +0530 [thread overview]
Message-ID: <20240101154624.100981-1-sshegde@linux.vnet.ibm.com> (raw)
Split the patches into two since there is subtle change with avg_irq.
There is no functionality change expected due to first patch, while
second patch may have. In case of any future regressions it would be
easy to bisect.
This is minor code simplification. Using existing helper function would
be simpler and easier to maintain.
v2->v1:
Vincent pointed out the READ_ONCE change for avg_irq. It would be
correct to use READ_ONCE for accessing avg_irq. Changed the current
helper function to do so.
v1: https://lore.kernel.org/lkml/20231220065522.351915-1-sshegde@linux.vnet.ibm.com/
Shrikanth Hegde (2):
sched: use existing helper functions to access ->avg_rt and ->avg_dl
sched: add READ_ONCE and use existing helper function to access ->avg_irq
kernel/sched/fair.c | 12 +++++-------
kernel/sched/sched.h | 2 +-
2 files changed, 6 insertions(+), 8 deletions(-)
--
2.39.3
next reply other threads:[~2024-01-01 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 15:46 Shrikanth Hegde [this message]
2024-01-01 15:46 ` [PATCH v2 1/2] sched: use existing helper functions to access ->avg_rt and ->avg_dl Shrikanth Hegde
2024-01-04 14:27 ` Vincent Guittot
2024-02-28 22:00 ` [tip: sched/core] sched/fair: Use " tip-bot2 for Shrikanth Hegde
2024-01-01 15:46 ` [PATCH v2 2/2] sched: add READ_ONCE and use existing helper function to access ->avg_irq Shrikanth Hegde
2024-01-04 14:28 ` Vincent Guittot
2024-02-28 22:00 ` [tip: sched/core] sched/fair: Add READ_ONCE() " tip-bot2 for Shrikanth Hegde
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=20240101154624.100981-1-sshegde@linux.vnet.ibm.com \
--to=sshegde@linux.vnet.ibm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=yu.c.chen@intel.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®