Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752296AbbFKHgK (ORCPT ); Thu, 11 Jun 2015 03:36:10 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:35482 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750966AbbFKHgD (ORCPT ); Thu, 11 Jun 2015 03:36:03 -0400 Message-ID: <1434008159.3411.50.camel@gmail.com> Subject: Re: RFC: futex_wait() can DoS the tick From: Mike Galbraith To: Thomas Gleixner Cc: LKML , Peter Zijlstra , Ingo Molnar , Steven Rostedt Date: Thu, 11 Jun 2015 09:35:59 +0200 In-Reply-To: References: <1433940278.6814.66.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 821 Lines: 20 On Wed, 2015-06-10 at 17:12 +0200, Thomas Gleixner wrote: > I just booted a SNB with lapic=notscdeadline and ran that test > program. All what happens is - as expected - that ksoftirqd runs more > than we would like it to. I cannot observe any anomality vs. local > timer interrupts at all. Ditto on a E5-4620 box this morning, no sign of it. E5-2670 box I had verified "went away" when I put master on it this morning, but that doesn't matter much, having deadline timer feature alone definitely doesn't mean box can be convinced to reproduce the stall. Hohum. -Mike -- 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/