From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1755940AbdLVOyE (ORCPT <rfc822;w@1wt.eu>);
        Fri, 22 Dec 2017 09:54:04 -0500
Received: from Galois.linutronix.de ([146.0.238.70]:57825 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752594AbdLVOyA (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 22 Dec 2017 09:54:00 -0500
Message-Id: <20171222145111.919609918@linutronix.de>
User-Agent: quilt/0.63-1
Date: Fri, 22 Dec 2017 15:51:11 +0100
From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Anna-Maria Gleixner <anna-maria@linutronix.de>,
        Sebastian Siewior <bigeasy@linutronix.de>,
        Paul McKenney <paulmck@linux.vnet.ibm.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Frederic Weisbecker <fweisbec@gmail.com>,
        Ingo Molnar <mingo@kernel.org>
Subject: [patch 0/4] timer/nohz: Fix timer/nohz woes
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Paul was observing weird stalls which are hard to reproduce and decode. We
were finally able to reproduce and decode the wreckage on RT.

The following series addresses the issues and hopefully nails the root
cause completely.

Please review carefully and expose it to the dreaded rcu torture tests
which seem to be the only way to trigger it.

Thanks,

	tglx