All of
 help / color / mirror / Atom feed
Subject: [to-be-updated] kfence-use-power-efficient-work-queue-to-run-delayed-work.patch removed from -mm tree
Date: Wed, 21 Apr 2021 21:15:06 -0700	[thread overview]
Message-ID: <> (raw)

The patch titled
     Subject: kfence: use power-efficient work queue to run delayed work
has been removed from the -mm tree.  Its filename was

This patch was dropped because an updated version will be merged

From: Marco Elver <>
Subject: kfence: use power-efficient work queue to run delayed work

Use the power-efficient work queue, to avoid the pathological case where
we keep pinning ourselves on the same possibly idle CPU on systems that
want to be power-efficient (

Signed-off-by: Marco Elver <>
Cc: Alexander Potapenko <>
Cc: Dmitry Vyukov <>
Cc: Jann Horn <>
Cc: Mark Rutland <>
Cc: Hillf Danton <>
Signed-off-by: Andrew Morton <>

 mm/kfence/core.c |    5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

--- a/mm/kfence/core.c~kfence-use-power-efficient-work-queue-to-run-delayed-work
+++ a/mm/kfence/core.c
@@ -642,7 +642,8 @@ static void toggle_allocation_gate(struc
 	/* Disable static key and reset timer. */
-	schedule_delayed_work(&kfence_timer, msecs_to_jiffies(kfence_sample_interval));
+	queue_delayed_work(system_power_efficient_wq, &kfence_timer,
+			   msecs_to_jiffies(kfence_sample_interval));
 static DECLARE_DELAYED_WORK(kfence_timer, toggle_allocation_gate);
@@ -671,7 +672,7 @@ void __init kfence_init(void)
 	WRITE_ONCE(kfence_enabled, true);
-	schedule_delayed_work(&kfence_timer, 0);
+	queue_delayed_work(system_power_efficient_wq, &kfence_timer, 0);
 	pr_info("initialized - using %lu bytes for %d objects at 0x%p-0x%p\n", KFENCE_POOL_SIZE,
 		CONFIG_KFENCE_NUM_OBJECTS, (void *)__kfence_pool,
 		(void *)(__kfence_pool + KFENCE_POOL_SIZE));

Patches currently in -mm which might be from are


                 reply	other threads:[~2021-04-22  4:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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.