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 S932879AbbI3WDe (ORCPT <rfc822;w@1wt.eu>);
	Wed, 30 Sep 2015 18:03:34 -0400
Received: from www.linutronix.de ([62.245.132.108]:46184 "EHLO
	Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754572AbbI3WDa (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 30 Sep 2015 18:03:30 -0400
Date: Thu, 1 Oct 2015 00:02:38 +0200 (CEST)
From: Thomas Gleixner <tglx@linutronix.de>
To: Chris Metcalf <cmetcalf@ezchip.com>
cc: Andy Lutomirski <luto@amacapital.net>,
        Gilad Ben Yossef <giladb@ezchip.com>,
        Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Rik van Riel <riel@redhat.com>, Tejun Heo <tj@kernel.org>,
        Frederic Weisbecker <fweisbec@gmail.com>,
        "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
        Christoph Lameter <cl@linux.com>,
        Viresh Kumar <viresh.kumar@linaro.org>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Will Deacon <will.deacon@arm.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "H. Peter Anvin" <hpa@zytor.com>, X86 ML <x86@kernel.org>
Subject: Re: [PATCH v7 07/11] arch/x86: enable task isolation functionality
In-Reply-To: <560C4CF4.9090601@ezchip.com>
Message-ID: <alpine.DEB.2.11.1509302358120.4500@nanos>
References: <1443453446-7827-1-git-send-email-cmetcalf@ezchip.com> <1443453446-7827-8-git-send-email-cmetcalf@ezchip.com> <CALCETrWh2iW_sz7Bd+QqWa0OQZsrma_Dxk1zZEZUbpr9E+GuqA@mail.gmail.com> <5609B7C0.3010807@ezchip.com> <CALCETrVdZxkEeQd3=V6p_yLYL7T83Y3WfnhfVGi3GwTxF+vPQg@mail.gmail.com>
 <560ACD6F.7060102@ezchip.com> <CALCETrUaUOLpFqFbPcPRh=nf57XfpXU=QfMvD9YvQE8rSZikGg@mail.gmail.com> <alpine.DEB.2.11.1509302205030.4500@nanos> <560C4CF4.9090601@ezchip.com>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Linutronix-Spam-Score: -1.0
X-Linutronix-Spam-Level: -
X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required,  ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 30 Sep 2015, Chris Metcalf wrote:
> So for now, if a task-isolation thread sets up a timer,
> they're screwed: so, don't do that.  And it's really not part of
> the typical programming model for these kinds of userspace
> drivers anyway, so it's pretty reasonable to forbid it.

There is a difference between forbidding it and looping for 10 minutes
in the kernel.

I have yet to understand WHY this loop is there at all. All I've seen
so far is that things might need to settle and that the indicator for
settlement is that the next expiry time of the per cpu timer is set to
KTIME_MAX.

To be blunt, that just stinks. This is duct tape engineering and not
even close to a reasonable design.

Thanks,

	tglx