public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Prasad Sodagudi <psodagud@codeaurora.org>
To: tglx@linutronix.de, john.stultz@linaro.org, sboyd@kernel.org,
	tj@kernel.org
Cc: linux-kernel@vger.kernel.org, saravanak@google.com,
	psodagud@codeaurora.org, pkondeti@codeaurora.org
Subject: [PATCH v3 0/2] timer: make deferrable cpu unbound timers really not bound to a cpu
Date: Sat,  2 May 2020 11:28:55 -0700	[thread overview]
Message-ID: <1588444137-18651-1-git-send-email-psodagud@codeaurora.org> (raw)

These patches are introducing support for global deferrable timers
and this feature is very useful for the mobile chipsets. All comments
in initial discussion [1] are addressed. Here is the latest discussion - [2]
as these  patches are in downstream kernel for quite a long time.

[1]- https://lore.kernel.org/patchwork/patch/500541/
[2]- https://lkml.org/lkml/2020/3/16/147

Changelog:
v2 -> v3:
 - Fixed 'kbuild test robot' warnings.

v1 -> v2:
 - Fixed tglx comments about warning.
 - Thanks Pavan for your suggestion.

Joonwoo Park (1):
  timer: make deferrable cpu unbound timers really not bound to a cpu

Prasad Sodagudi (1):
  sched: Add a check for cpu unbound deferrable timers

 include/linux/timer.h    |  3 +++
 kernel/time/tick-sched.c |  8 +++++-
 kernel/time/timer.c      | 69 ++++++++++++++++++++++++++++++++++++++++++++----
 3 files changed, 74 insertions(+), 6 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

             reply	other threads:[~2020-05-02 18:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 18:28 Prasad Sodagudi [this message]
2020-05-02 18:28 ` [PATCH v3 1/2] timer: make deferrable cpu unbound timers really not bound to a cpu Prasad Sodagudi
2020-05-04 18:11   ` kbuild test robot
2020-05-05  0:08   ` kbuild test robot
2020-05-06 13:28   ` Thomas Gleixner
2020-05-13 19:53     ` psodagud
2020-05-13 20:28       ` Thomas Gleixner
2020-05-13 20:55         ` psodagud
2020-05-13 21:34           ` Thomas Gleixner
2020-05-02 18:28 ` [PATCH v3 2/2] sched: Add a check for cpu unbound deferrable timers Prasad Sodagudi
2020-05-04 19:11   ` kbuild test robot
2020-05-06 14:03   ` Thomas Gleixner

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=1588444137-18651-1-git-send-email-psodagud@codeaurora.org \
    --to=psodagud@codeaurora.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pkondeti@codeaurora.org \
    --cc=saravanak@google.com \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tj@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