Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946104AbbDXP6l (ORCPT ); Fri, 24 Apr 2015 11:58:41 -0400 Received: from mail-wg0-f51.google.com ([74.125.82.51]:34387 "EHLO mail-wg0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1946078AbbDXP6h (ORCPT ); Fri, 24 Apr 2015 11:58:37 -0400 From: Frederic Weisbecker To: LKML Cc: Frederic Weisbecker , "Rafael J . Wysocki" , Peter Zijlstra , Mike Galbraith , Chris Metcalf , Ingo Molnar , Dave Jones , Thomas Gleixner , Oleg Nesterov , "Paul E . McKenney" , Ingo Molnar , Rik van Riel , Martin Schwidefsky Subject: [PATCH 0/4] nohz: A few improvements v3 Date: Fri, 24 Apr 2015 17:58:27 +0200 Message-Id: <1429891111-30855-1-git-send-email-fweisbec@gmail.com> X-Mailer: git-send-email 2.1.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1267 Lines: 37 Since v2, this set only changes "context_tracking: Inherit TIF_NOHZ through forks instead of context switches" which now warns when tasklist is populated earlier than expected as per Peterz suggestion. Simpler. git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git nohz/core HEAD: 3c2b3b78a1cca2865a932d0265690997db9706b1 Thanks, Frederic --- Chris Metcalf (2): nohz: Add tick_nohz_full_add_cpus_to() API nohz: Set isolcpus when nohz_full is set Frederic Weisbecker (2): context_tracking: Protect against recursion context_tracking: Inherit TIF_NOHZ through forks instead of context switches include/linux/context_tracking.h | 10 ----- include/linux/context_tracking_state.h | 1 + include/linux/sched.h | 3 ++ include/linux/tick.h | 7 ++++ kernel/context_tracking.c | 69 +++++++++++++++++++++++----------- kernel/sched/core.c | 4 +- 6 files changed, 61 insertions(+), 33 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/