From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,UNPARSEABLE_RELAY,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 842DAC43387 for ; Thu, 10 Jan 2019 07:54:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5EB3320685 for ; Thu, 10 Jan 2019 07:54:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727645AbfAJHyy (ORCPT ); Thu, 10 Jan 2019 02:54:54 -0500 Received: from eddie.linux-mips.org ([148.251.95.138]:48518 "EHLO cvs.linux-mips.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726137AbfAJHyu (ORCPT ); Thu, 10 Jan 2019 02:54:50 -0500 Received: (from localhost user: 'ladis' uid#1021 fake: STDIN (ladis@eddie.linux-mips.org)) by eddie.linux-mips.org id S23990945AbfAJHysH0baQ (ORCPT + 2 others); Thu, 10 Jan 2019 08:54:48 +0100 Date: Thu, 10 Jan 2019 08:54:44 +0100 From: Ladislav Michl To: Vincent Guittot Cc: "Rafael J. Wysocki" , Tony Lindgren , "Rafael J. Wysocki" , Ulf Hansson , "open list:THERMAL" , linux-kernel , LAK , Linux OMAP Mailing List Subject: Re: Regression in v5.0-rc1 with autosuspend hrtimers Message-ID: <20190110075444.GA26920@lenoch> References: <20190109133337.GA13579@lenoch> <20190109160736.GA7416@lenoch> <20190109172623.GB1711@lenoch> <20190110074558.GA26167@lenoch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 10, 2019 at 08:50:14AM +0100, Vincent Guittot wrote: > On Thu, 10 Jan 2019 at 08:46, Ladislav Michl wrote: > > > > On Wed, Jan 09, 2019 at 11:06:34PM +0100, Rafael J. Wysocki wrote: > > > On Wed, Jan 9, 2019 at 7:05 PM Vincent Guittot > > > wrote: > > > > > > > > On Wed, 9 Jan 2019 at 18:26, Ladislav Michl wrote: > > > > > > > > > > On Wed, Jan 09, 2019 at 05:32:31PM +0100, Vincent Guittot wrote: > > > > > > On Wed, 9 Jan 2019 at 17:07, Ladislav Michl wrote: > > > > > > > > > > > > > > On Wed, Jan 09, 2019 at 03:12:25PM +0100, Vincent Guittot wrote: > > > > > > > > Please keep all thread list when replying :-) > > > > > > > > > > > > > > Ahh, sorry for that... > > > > > > > [snip] > > > > > > > > On Wed, 9 Jan 2019 at 14:33, Ladislav Michl wrote: > > > > > > > > > I agree, but it doea all the magic correctly, so you won't need > > > > > > > > > to touch that code is ktime_t changes (I know, unlikely..) > > > > > > > > > > > > > > > > But the current implementation doesn't care of any changes in ktime_t > > > > > > > > as it uses raw ns > > > > > > > > > > > > > > Fair enough, so let's go back to: > > > > > > > > > > > > This one looks good for me > > > > > > > > > > Lets split is for 'comments fix' patch, which was just send and 'the rest'. > > > > > Now, 'the rest' can either be v2 of your "PM/runtime: Fix autosuspend_delay on > > > > > 32bits arch" or will wait for 5.1. You decide :) > > > > > > > > I don't really mind. > > > > > > > > Rafael, > > > > Do you prefer to only take the fix for u64 casting problem or do you > > > > prefer to also take the optimization below in one single patch ? > > > > > > The casting problem is a bug and the optimization is next release > > > material in my view. Please send the optimization separately. > > > > Ok, will send that separately in a few moments... > > Btw, u64 casting problem seems to be still present in rpm_suspend while > > computing slack for autosuspend delay greater than 25% of 2^31 (2^33) ns. > > Good point. I will add it to the fix as well Another nit then, for (u64)(autosuspend_delay) is (u64)autosuspend_delay enough :) I'll wait for your v2 before sending optimization patch. > > Not sure if that triggers any real bug.