public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <frederic@kernel.org>,
	Wanpeng Li <wanpengli@tencent.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Yauheni Kaliuta <yauheni.kaliuta@redhat.com>,
	Rik van Riel <riel@redhat.com>
Subject: [PATCH 0/2] vtime: Remove pair of seqcount on context switch
Date: Thu,  3 Oct 2019 18:17:43 +0200	[thread overview]
Message-ID: <20191003161745.28464-1-frederic@kernel.org> (raw)

Extracted from a larger queue that fixes kcpustat on nohz_full, these
two patches have value on their own as they remove two write barriers
on nohz_full context switch.

Frederic Weisbecker (2):
  vtime: Rename vtime_account_system() to vtime_account_kernel()
  vtime: Spare a seqcount lock/unlock cycle on context switch

 arch/ia64/kernel/time.c          |  4 +--
 arch/powerpc/kernel/time.c       |  6 ++--
 arch/s390/kernel/vtime.c         |  4 +--
 include/linux/context_tracking.h |  4 +--
 include/linux/vtime.h            | 38 ++++++++++++------------
 kernel/sched/cputime.c           | 50 ++++++++++++++++++--------------
 6 files changed, 57 insertions(+), 49 deletions(-)

-- 
2.23.0


             reply	other threads:[~2019-10-03 16:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 16:17 Frederic Weisbecker [this message]
2019-10-03 16:17 ` [PATCH 1/2] vtime: Rename vtime_account_system() to vtime_account_kernel() Frederic Weisbecker
2019-10-09 12:59   ` [tip: sched/core] sched/cputime: " tip-bot2 for Frederic Weisbecker
2019-10-03 16:17 ` [PATCH 2/2] vtime: Spare a seqcount lock/unlock cycle on context switch Frederic Weisbecker
2019-10-09 12:59   ` [tip: sched/core] sched/cputime: " tip-bot2 for Frederic Weisbecker
2019-10-07 16:20 ` [PATCH 0/2] vtime: Remove pair of seqcount " Ingo Molnar
2019-10-07 16:51   ` Frederic Weisbecker

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=20191003161745.28464-1-frederic@kernel.org \
    --to=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=wanpengli@tencent.com \
    --cc=yauheni.kaliuta@redhat.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