mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Wanpeng Li <wanpeng.li@hotmail.com>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	Ingo Molnar <mingo@kernel.org>, Mike Galbraith <efault@gmx.de>,
	Rik van Riel <riel@redhat.com>
Subject: [PATCH 0/5] sched/cputime: irqtime cleanups v2
Date: Mon, 26 Sep 2016 02:29:16 +0200	[thread overview]
Message-ID: <1474849761-12678-1-git-send-email-fweisbec@gmail.com> (raw)

This second version fixes the ifdeffery issues reported by Paolo Bonzini
and includes Rick's reviewed-by tags.

I also intended to include Peterz's patch for lockdep assertion on irqs
disabled but unfortunately I get false positives as irqs_disabled()
doesn't always imply !current->hardirqs_enabled. This seems to happen
during the boot with IRQs interrupting lockdep internals while
current->lockdep_recursion == 1. Therefore the trace_hardirqs_off() on
x86 IRQ entry gets ignored. I'll investigate further and try to get
that fixed in order to introduce lockdep_assert_irqs_disabled() properly
but that's outside the scope of this patchset now.

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
	sched/irqtime-v2

HEAD: e336b2491bf02e95ff3387e7d7a8276b22c8b5f3

Thanks,
	Frederic
---

Frederic Weisbecker (5):
      irqtime: No need for preempt-safe accessors
      irqtime: Remove needless IRQs disablement on kcpustat update
      u64_stats: Introduce IRQs disabled helpers
      irqtime: Consolidate accounting synchronization with u64_stats API
      irqtime: Consolidate irqtime flushing code


 include/linux/u64_stats_sync.h | 45 +++++++++++++++++++----------------
 kernel/sched/cputime.c         | 54 ++++++++++++++++++------------------------
 kernel/sched/sched.h           | 53 ++++++++++++-----------------------------
 3 files changed, 62 insertions(+), 90 deletions(-)

             reply	other threads:[~2016-09-26  0:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26  0:29 Frederic Weisbecker [this message]
2016-09-26  0:29 ` [PATCH 1/5] irqtime: No need for preempt-safe accessors Frederic Weisbecker
2016-09-30 12:04   ` [tip:sched/core] sched/irqtime: " tip-bot for Frederic Weisbecker
2016-09-26  0:29 ` [PATCH 2/5] irqtime: Remove needless IRQs disablement on kcpustat update Frederic Weisbecker
2016-09-30 12:05   ` [tip:sched/core] sched/irqtime: " tip-bot for Frederic Weisbecker
2016-09-26  0:29 ` [PATCH 3/5] u64_stats: Introduce IRQs disabled helpers Frederic Weisbecker
2016-09-30 12:05   ` [tip:sched/core] " tip-bot for Frederic Weisbecker
2016-09-26  0:29 ` [PATCH 4/5] irqtime: Consolidate accounting synchronization with u64_stats API Frederic Weisbecker
2016-09-30 12:05   ` [tip:sched/core] sched/irqtime: " tip-bot for Frederic Weisbecker
2016-09-26  0:29 ` [PATCH 5/5] irqtime: Consolidate irqtime flushing code Frederic Weisbecker
2016-09-30 12:06   ` [tip:sched/core] sched/irqtime: " tip-bot for 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=1474849761-12678-1-git-send-email-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=efault@gmx.de \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=wanpeng.li@hotmail.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®