Received: by 10.223.185.116 with SMTP id b49csp7790683wrg; Thu, 1 Mar 2018 11:08:00 -0800 (PST) X-Google-Smtp-Source: AG47ELtt7lVxb7vTfXhRVzAgv/pNnWkNwcB6M7wIRn+X5ggRHLk6K2JfGfEXu5kQmOYQtAjj9oEv X-Received: by 2002:a17:902:b787:: with SMTP id e7-v6mr2851025pls.317.1519931280514; Thu, 01 Mar 2018 11:08:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519931280; cv=none; d=google.com; s=arc-20160816; b=KePgdNdKHMfKzyekiMiT0mD01t24hzWAj+CGWS+NRz0ckX2eSby4Vx2fQmrq+qY1m1 Oye/j99ESjHePyxJrUqSTEkD3s0EhlMEoRrzm1TNKhZ++7disCz8kWVlrHhQxy2WMJ51 woba6at5Y8qzwkHspLl3lH0+cCfuueRwz5pmtVlDeU2KR8In4q/DqUlOsRys5PuHVxIg MXmi29BEDJMaKcYAvsXsvQA/4cQ3A+FgmsxGKFsryqRFEKXkGcI/20Wv4fY0vV3rHjqN Nc7HOot+C4XgbGwDfUb7fuvq5evCb1z+CXXhSXgh84uQxiDgh6HVN0Zb2V80/4yhg7mI m00g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=bzo9c6NDXA5fLiT56h7YA5qpbOmdPjnKwyZjTm58nF4=; b=o5nWGpvrRFLNIZkJRMLQtJdhnnSAxNMdHU+D/e9s1K8belikTlTD2zSIwJTeBNFcru bP7Bs+pQ4N/NPnoNUWK+wCuctsMfM3O3QFNmDHif9Bg170JzgrTFpXHMROkX44dv0/rQ QKVppmrLETArghTljEPZ8lpTB8qXyLHwjEF1L11zrDmfvKSmUChTIP0dZT9PLArbeEWu r/rRhuvrmiFWhSX9ksPELy3Wg2L2ywE1v2twfBdZ4Jm3utfMZFuk//+DySQZmlFSwlVW ZrKnazmkkY/roWsMSfx8zrpIeZ14FqO9hvjQjnfV9m1eWzn2P4hF64sjBOQq3/Qw+8Rv xm1g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s26si3455223pfg.264.2018.03.01.11.07.45; Thu, 01 Mar 2018 11:08:00 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161139AbeCATGn (ORCPT + 99 others); Thu, 1 Mar 2018 14:06:43 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:52213 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161068AbeCATGm (ORCPT ); Thu, 1 Mar 2018 14:06:42 -0500 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1erTTp-0002Ki-79; Thu, 01 Mar 2018 20:03:01 +0100 Date: Thu, 1 Mar 2018 20:06:39 +0100 From: Sebastian Andrzej Siewior To: Haris Okanovic Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de, julia.cartwright@ni.com, gratian.crisan@ni.com, anna-maria@linutronix.de Subject: Re: [PATCH v3 2/2] timers: Don't search for expired timers while TIMER_SOFTIRQ is scheduled Message-ID: <20180301190639.fttlaq272p67qzm4@linutronix.de> References: <20170803210657.19179-1-haris.okanovic@ni.com> <20170803210657.19179-2-haris.okanovic@ni.com> <28f05e39-6bc6-99c5-e1bc-91be3e79ea78@ni.com> <13c06708-f7ad-4f46-1c0b-f12d1ca16beb@ni.com> <20180301164755.pipco45y5nlvmdsy@linutronix.de> <7079102c-f53b-e8ab-c54d-1c40ff21d921@ni.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <7079102c-f53b-e8ab-c54d-1c40ff21d921@ni.com> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018-03-01 12:37:49 [-0600], Haris Okanovic wrote: > On 03/01/2018 10:47 AM, Sebastian Andrzej Siewior wrote: > > On 2018-03-01 09:49:59 [-0600], Haris Okanovic wrote: > > > *bump* Has anyone looked into this? > > > > I'm lost. > > It entered the kernel in v4.9.9-rt6 and left in v4.9.30-rt20 once we > > figured out that there is something wrong with it. > > It was added back into 4.9 at some point after v4.9.30-rt20. I see an older > version in v4.9.68-rt60, for example, hence my original email. It was let me check that tomorrow. > dropped sometime thereafter, presumably because it no longer cleanly > applies. I don't see it in v4.14.20-rt17, for example. > > > Is there a newer patch pending on your side? > > Not yet. The latest version on patchwork is OK, just needs to be rebased > post-4.9. I'll post a new version when I get a chance to build and retest > it. okay. Sebastian