From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935141AbdCWPF2 (ORCPT ); Thu, 23 Mar 2017 11:05:28 -0400 Received: from merlin.infradead.org ([205.233.59.134]:42674 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754187AbdCWPFX (ORCPT ); Thu, 23 Mar 2017 11:05:23 -0400 Message-Id: <20170323145606.480214279@infradead.org> User-Agent: quilt/0.63-1 Date: Thu, 23 Mar 2017 15:56:06 +0100 From: Peter Zijlstra To: mingo@kernel.org, tglx@linutronix.de, juri.lelli@arm.com, rostedt@goodmis.org, xlpang@redhat.com, bigeasy@linutronix.de Cc: linux-kernel@vger.kernel.org, mathieu.desnoyers@efficios.com, jdesfossez@efficios.com, bristot@redhat.com, peterz@infradead.org Subject: [PATCH -v3 0/8] PI vs SCHED_DEADLINE fixes Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Now that this pesky little problem with futexes is (hopefully) dealt with; https://lkml.kernel.org/r/20170322103547.756091212@infradead.org We can get on with fixing the actual bug this all started out with. These patches, started by Xunlei Pang, rework the PI infrastructure a bit fixing various problems it has, most notable a NULL deref in SCHED_DEADLINE. Once this is sorted; we can look at improving the tracing thing (Daniel Bristot and Julien Desfossez were working on that) and have a better foundation to look at bandwidth inheritance (Juri and co.).