mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qais Yousef <qais.yousef@arm.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Mel Gorman <mgorman@suse.de>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Qais Yousef <qais.yousef@arm.com>
Subject: [PATCH 0/2] Backport uclamp static key to 5.4.y stable
Date: Fri, 28 Aug 2020 13:56:08 +0100	[thread overview]
Message-ID: <20200828125610.30943-1-qais.yousef@arm.com> (raw)

Hi Greg/Sasha

The following 2 patches are backports of

	46609ce22703: ("sched/uclamp: Protect uclamp fast path code with static key")
	e65855a52b47: ("sched/uclamp: Fix a deadlock when enabling uclamp static key")

into 5.4.y stable tree. The conflict was trivial and due to:

	1. uclamp_rq_util_with() was renamed from util_util_with()
	2. 2 local variables were converted to unsigned long from unsigned int.

I did do compile test on aarch64 and x86_64 and both looked fine. Beside I ran
a quick and short mmtest to verify the functionality and got the following
results which is inline with what's expected.

                        5.4.y                  5.4.y-static-keys
Hmean     send-64       188.46 (   0.00%)      189.95 *   0.79%*
Hmean     send-128      375.65 (   0.00%)      379.75 *   1.09%*

7.32%     -0.33%  [kernel.kallsyms]        [k] try_to_wake_up
0.58%     -0.55%  [kernel.kallsyms]        [k] deactivate_task
0.50%     -0.45%  [kernel.kallsyms]        [k] activate_task


That said, it's Friday afternoon and I am off next week. If I did something
stupid and didn't find me, please accept my apologies in advance and will fix
it as soon as I am back online.

Thanks

--
Qais Yousef


Qais Yousef (2):
  sched/uclamp: Protect uclamp fast path code with static key
  sched/uclamp: Fix a deadlock when enabling uclamp static key

 kernel/sched/core.c              | 81 +++++++++++++++++++++++++++++++-
 kernel/sched/cpufreq_schedutil.c |  2 +-
 kernel/sched/sched.h             | 47 +++++++++++++++++-
 3 files changed, 126 insertions(+), 4 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-08-28 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 12:56 Qais Yousef [this message]
2020-08-28 12:56 ` [PATCH 1/2] sched/uclamp: Protect uclamp fast path code with static key Qais Yousef
2020-08-28 12:56 ` [PATCH 2/2] sched/uclamp: Fix a deadlock when enabling uclamp " Qais Yousef
2020-08-28 16:36 ` [PATCH 0/2] Backport uclamp static key to 5.4.y stable Sasha Levin

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=20200828125610.30943-1-qais.yousef@arm.com \
    --to=qais.yousef@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=peterz@infradead.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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®