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=-9.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable 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 E5DE5C4742C for ; Fri, 30 Oct 2020 20:37:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8EBFD208B6 for ; Fri, 30 Oct 2020 20:37:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604090273; bh=KMeucbRcvCAihtlPektQKjQQmEbPkfEfXwxxqluaaUQ=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=ctqNupeQ/UuPWPV1zbm0qv9L534yMGy2Mkm8DvOEOpJ8z/1WZfRFolKxoalhXOOj1 5KGjRa60cYJTVf9cKzqqibGhZDix9ZSxV2tvdk6iaMXWchvlQ6UeDGnDeEeY7BOYQU T45QthnT1EZtN5Vgw0d6IUyRPIJ56pqp3SDcOpRQ= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727344AbgJ3Uhx (ORCPT ); Fri, 30 Oct 2020 16:37:53 -0400 Received: from mail.kernel.org ([198.145.29.99]:50714 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727205AbgJ3Uhx (ORCPT ); Fri, 30 Oct 2020 16:37:53 -0400 Received: from mail-qk1-f176.google.com (mail-qk1-f176.google.com [209.85.222.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D3CDC22202; Fri, 30 Oct 2020 20:37:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604090272; bh=KMeucbRcvCAihtlPektQKjQQmEbPkfEfXwxxqluaaUQ=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=n0aOfPqikD2DqyDNtRdaMMz7zhgr2XFWvlOW8+szCciZ5IZ8WuBMCbDXaTreNOhYd drDknWEy+B/EaXYzq5iB3C7eEB5kYGx8pLc4oN9CU7d1t1kT1X64Yy9dWE2pXXHTOA G8RJawjTEvYxNFoGoVoK9qn4pWo9Mc5PTx0Qdo+w= Received: by mail-qk1-f176.google.com with SMTP id a64so2754066qkc.5; Fri, 30 Oct 2020 13:37:51 -0700 (PDT) X-Gm-Message-State: AOAM532yFFpy7QyyLX+gbCSHHioLAcA4NL7gZ0NaQvbkgAJLMOyyXuSr Cj8izF7fDS/91wYsBh0mTe+Wg3ElKglIr0B/DAM= X-Google-Smtp-Source: ABdhPJw19dZY4Xih4GL4dANiN8uMa27xGqxcu4F9ebbgd48VSQ+Qm0ZF3KNUOEKXfjfqBfqrvnQ2vDND7Ej01f3sHHE= X-Received: by 2002:a05:620a:22c9:: with SMTP id o9mr4110937qki.286.1604090270867; Fri, 30 Oct 2020 13:37:50 -0700 (PDT) MIME-Version: 1.0 References: <20201030151758.1241164-1-arnd@kernel.org> <20201030151758.1241164-8-arnd@kernel.org> <2e2d7b65-0aa8-55aa-d395-52cfb048adef@gmx.de> In-Reply-To: From: Arnd Bergmann Date: Fri, 30 Oct 2020 21:37:34 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 07/15] parisc: use legacy_timer_tick To: Helge Deller Cc: "linux-kernel@vger.kernel.org" , Thomas Gleixner , Arnd Bergmann , Russell King , Tony Luck , Fenghua Yu , Greg Ungerer , Finn Thain , Philip Blundell , Joshua Thompson , Sam Creasey , "James E.J. Bottomley" , Daniel Lezcano , John Stultz , Stephen Boyd , Linus Walleij , linux-ia64@vger.kernel.org, Parisc List , linux-m68k , Linux ARM Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-parisc@vger.kernel.org On Fri, Oct 30, 2020 at 8:48 PM Helge Deller wrote: > On 10/30/20 8:33 PM, Arnd Bergmann wrote: > > On Fri, Oct 30, 2020 at 6:13 PM Helge Deller wrote: > >> > >> On 10/30/20 4:17 PM, Arnd Bergmann wrote: > >>> From: Arnd Bergmann > >>> > >>> parisc has selected CONFIG_GENERIC_CLOCKEVENTS since commit 43b1f6abd590 > >>> ("parisc: Switch to generic sched_clock implementation"), but does not > >>> appear to actually be using it, and instead calls the low-level > >>> timekeeping functions directly. > >> > >> Arnd, thank you for this patch! > >> It reminded me that I really missed to fully implement the clockevents on parisc! > >> > >> Your other patch ("RFC: m68k: mac: convert to generic clockevent") > >> was a big help too, as it showed how it might work on parisc as well. > >> > >> Here is now a current version of the clockevents-enabling-patch for parisc: > >> https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/commit/?h=for-next&id=3b7ab4a74a2d1972dbeb33285d85f1500b2ff96a > > > > Ah, nice! > > > >>> Remove the GENERIC_CLOCKEVENTS select again, and instead convert to > >>> the newly added legacy_timer_tick() helper. > >> > >> My patch still needs more testing, but if it turns to work > >> out right, would you mind to drop your patch for parisc? > > > > I think it would be easier if you could base your patch on top of > > my series, as they would otherwise inevitably conflict. I could either > > add it to my tree, or you could merge my branch into your tree. > > Couldn't you drop your patch and include mine in your tree instead? > That way nothing conflicts, and they get merged together? That only works if nobody merges this branch into another one, otherwise we end up with multiple copies of the later commits. Arnd 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=-9.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED 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 83CB8C388F9 for ; Fri, 30 Oct 2020 20:38:29 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id C258320797 for ; Fri, 30 Oct 2020 20:38:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="VEiIyeK3"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="n0aOfPqi" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C258320797 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From:In-Reply-To: References:MIME-Version:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=xvyR1gjzWkltVJWREmBozPzwa8rr2WcAZnmn+PiDF8c=; b=VEiIyeK3HthpQTOxbNulQfK0M lylsJ+E7D0h45o+xoApOZQ596uohJvbyDIBv9M/5ba1cY/ncoJqIRWtOShDqPOipDleSgkmKtcVTs nw3oCSZpk7L9X5xvMAZtqmmQD+ZV/EliaTTB7htYK/OEsq1YA7q2zgMnY9o/LJF+/iKyQnJsU42E8 Jzs+I/nRANF2OZbM1PmwhFFIDu1LwijkfGu/HgzO3TjU6yNUFWbYGzHiVTqRPEDhkPYYdh/KHMqmP HvAfQJ/N8LsHYWX06w5L3BqH0htBxXEScbPq+kog4VAJFoCWkUmrWpQqGKG+bZFBgi+yI1TbQOjfr a/zsKkhkw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kYb9o-0003OP-OV; Fri, 30 Oct 2020 20:37:56 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kYb9l-0003NX-Rk for linux-arm-kernel@lists.infradead.org; Fri, 30 Oct 2020 20:37:55 +0000 Received: from mail-qk1-f179.google.com (mail-qk1-f179.google.com [209.85.222.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id DD6EF22241 for ; Fri, 30 Oct 2020 20:37:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1604090272; bh=KMeucbRcvCAihtlPektQKjQQmEbPkfEfXwxxqluaaUQ=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=n0aOfPqikD2DqyDNtRdaMMz7zhgr2XFWvlOW8+szCciZ5IZ8WuBMCbDXaTreNOhYd drDknWEy+B/EaXYzq5iB3C7eEB5kYGx8pLc4oN9CU7d1t1kT1X64Yy9dWE2pXXHTOA G8RJawjTEvYxNFoGoVoK9qn4pWo9Mc5PTx0Qdo+w= Received: by mail-qk1-f179.google.com with SMTP id 12so2232552qkl.8 for ; Fri, 30 Oct 2020 13:37:51 -0700 (PDT) X-Gm-Message-State: AOAM531u1SYH00YoH7shTxTU9uDcA80CJ11n2FSMHD1HOv//F4Is+vsb x2D+22orSlX0r9L2PS0lxctvlPEmHnKUwqcRgOM= X-Google-Smtp-Source: ABdhPJw19dZY4Xih4GL4dANiN8uMa27xGqxcu4F9ebbgd48VSQ+Qm0ZF3KNUOEKXfjfqBfqrvnQ2vDND7Ej01f3sHHE= X-Received: by 2002:a05:620a:22c9:: with SMTP id o9mr4110937qki.286.1604090270867; Fri, 30 Oct 2020 13:37:50 -0700 (PDT) MIME-Version: 1.0 References: <20201030151758.1241164-1-arnd@kernel.org> <20201030151758.1241164-8-arnd@kernel.org> <2e2d7b65-0aa8-55aa-d395-52cfb048adef@gmx.de> In-Reply-To: From: Arnd Bergmann Date: Fri, 30 Oct 2020 21:37:34 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 07/15] parisc: use legacy_timer_tick To: Helge Deller X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201030_163754_110226_27DE8330 X-CRM114-Status: GOOD ( 26.46 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Sam Creasey , Fenghua Yu , Tony Luck , linux-ia64@vger.kernel.org, Parisc List , Arnd Bergmann , Stephen Boyd , Philip Blundell , Linus Walleij , Daniel Lezcano , "linux-kernel@vger.kernel.org" , Finn Thain , Russell King , "James E.J. Bottomley" , linux-m68k , John Stultz , Linux ARM , Thomas Gleixner , Greg Ungerer , Joshua Thompson Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Oct 30, 2020 at 8:48 PM Helge Deller wrote: > On 10/30/20 8:33 PM, Arnd Bergmann wrote: > > On Fri, Oct 30, 2020 at 6:13 PM Helge Deller wrote: > >> > >> On 10/30/20 4:17 PM, Arnd Bergmann wrote: > >>> From: Arnd Bergmann > >>> > >>> parisc has selected CONFIG_GENERIC_CLOCKEVENTS since commit 43b1f6abd590 > >>> ("parisc: Switch to generic sched_clock implementation"), but does not > >>> appear to actually be using it, and instead calls the low-level > >>> timekeeping functions directly. > >> > >> Arnd, thank you for this patch! > >> It reminded me that I really missed to fully implement the clockevents on parisc! > >> > >> Your other patch ("RFC: m68k: mac: convert to generic clockevent") > >> was a big help too, as it showed how it might work on parisc as well. > >> > >> Here is now a current version of the clockevents-enabling-patch for parisc: > >> https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/commit/?h=for-next&id=3b7ab4a74a2d1972dbeb33285d85f1500b2ff96a > > > > Ah, nice! > > > >>> Remove the GENERIC_CLOCKEVENTS select again, and instead convert to > >>> the newly added legacy_timer_tick() helper. > >> > >> My patch still needs more testing, but if it turns to work > >> out right, would you mind to drop your patch for parisc? > > > > I think it would be easier if you could base your patch on top of > > my series, as they would otherwise inevitably conflict. I could either > > add it to my tree, or you could merge my branch into your tree. > > Couldn't you drop your patch and include mine in your tree instead? > That way nothing conflicts, and they get merged together? That only works if nobody merges this branch into another one, otherwise we end up with multiple copies of the later commits. Arnd _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Date: Fri, 30 Oct 2020 20:37:34 +0000 Subject: Re: [PATCH v2 07/15] parisc: use legacy_timer_tick Message-Id: List-Id: References: <20201030151758.1241164-1-arnd@kernel.org> <20201030151758.1241164-8-arnd@kernel.org> <2e2d7b65-0aa8-55aa-d395-52cfb048adef@gmx.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Helge Deller Cc: "linux-kernel@vger.kernel.org" , Thomas Gleixner , Arnd Bergmann , Russell King , Tony Luck , Fenghua Yu , Greg Ungerer , Finn Thain , Philip Blundell , Joshua Thompson , Sam Creasey , "James E.J. Bottomley" , Daniel Lezcano , John Stultz , Stephen Boyd , Linus Walleij , linux-ia64@vger.kernel.org, Parisc List , linux-m68k , Linux ARM On Fri, Oct 30, 2020 at 8:48 PM Helge Deller wrote: > On 10/30/20 8:33 PM, Arnd Bergmann wrote: > > On Fri, Oct 30, 2020 at 6:13 PM Helge Deller wrote: > >> > >> On 10/30/20 4:17 PM, Arnd Bergmann wrote: > >>> From: Arnd Bergmann > >>> > >>> parisc has selected CONFIG_GENERIC_CLOCKEVENTS since commit 43b1f6abd590 > >>> ("parisc: Switch to generic sched_clock implementation"), but does not > >>> appear to actually be using it, and instead calls the low-level > >>> timekeeping functions directly. > >> > >> Arnd, thank you for this patch! > >> It reminded me that I really missed to fully implement the clockevents on parisc! > >> > >> Your other patch ("RFC: m68k: mac: convert to generic clockevent") > >> was a big help too, as it showed how it might work on parisc as well. > >> > >> Here is now a current version of the clockevents-enabling-patch for parisc: > >> https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/commit/?h=for-next&id;7ab4a74a2d1972dbeb33285d85f1500b2ff96a > > > > Ah, nice! > > > >>> Remove the GENERIC_CLOCKEVENTS select again, and instead convert to > >>> the newly added legacy_timer_tick() helper. > >> > >> My patch still needs more testing, but if it turns to work > >> out right, would you mind to drop your patch for parisc? > > > > I think it would be easier if you could base your patch on top of > > my series, as they would otherwise inevitably conflict. I could either > > add it to my tree, or you could merge my branch into your tree. > > Couldn't you drop your patch and include mine in your tree instead? > That way nothing conflicts, and they get merged together? That only works if nobody merges this branch into another one, otherwise we end up with multiple copies of the later commits. Arnd