From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Rutland Subject: Re: [PATCH 0/4] ARM 64 bit sched_clock take #2 Date: Mon, 22 Apr 2013 16:34:08 +0100 Message-ID: <20130422153408.GD3791@e106331-lin.cambridge.arm.com> References: <51709FD7.8050408@gmail.com> <1366417746-24990-1-git-send-email-sboyd@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:62855 "EHLO cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754491Ab3DVPea (ORCPT ); Mon, 22 Apr 2013 11:34:30 -0400 Content-Disposition: inline In-Reply-To: <1366417746-24990-1-git-send-email-sboyd@codeaurora.org> Content-Language: en-US Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Stephen Boyd Cc: Rob Herring , Russell King , "linux-arm-msm@vger.kernel.org" , Will Deacon , "linux-kernel@vger.kernel.org" , "arm@kernel.org" , John Stultz , Catalin Marinas , Thomas Gleixner , "linux-arm-kernel@lists.infradead.org" Hi Stephen, On Sat, Apr 20, 2013 at 01:29:02AM +0100, Stephen Boyd wrote: > This is what I was thinking. I don't see why we can't move this to generic > code and have arm64 use it too. Those patches will follow once I find an > arm64 compiler. > > First two patches should probably go in even if the 64 bit stuff doesn't go in > at the same time. > > Stephen Boyd (4): > ARM: sched_clock: Remove unused needs_suspend member > ARM: sched_clock: Return suspended count earlier > ARM: sched_clock: Add support for >32 bit sched_clock > ARM: arch_timer: Move to setup_sched_clock_64() > > arch/arm/include/asm/sched_clock.h | 5 +- > arch/arm/kernel/arch_timer.c | 14 +---- > arch/arm/kernel/sched_clock.c | 111 ++++++++++++++++++++++++++----------- > 3 files changed, 84 insertions(+), 46 deletions(-) I wanted to look at the series with more context, but I don't seem to be able to apply patch 2 and beyond to my tree, and I couldn't figure out what tree this series was based on. What do I need to use as the base for this series? Thanks, Mark. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754543Ab3DVPec (ORCPT ); Mon, 22 Apr 2013 11:34:32 -0400 Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:62855 "EHLO cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754491Ab3DVPea (ORCPT ); Mon, 22 Apr 2013 11:34:30 -0400 Date: Mon, 22 Apr 2013 16:34:08 +0100 From: Mark Rutland To: Stephen Boyd Cc: Rob Herring , Russell King , "linux-arm-msm@vger.kernel.org" , Will Deacon , "linux-kernel@vger.kernel.org" , "arm@kernel.org" , John Stultz , Catalin Marinas , Thomas Gleixner , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH 0/4] ARM 64 bit sched_clock take #2 Message-ID: <20130422153408.GD3791@e106331-lin.cambridge.arm.com> References: <51709FD7.8050408@gmail.com> <1366417746-24990-1-git-send-email-sboyd@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1366417746-24990-1-git-send-email-sboyd@codeaurora.org> Thread-Topic: [PATCH 0/4] ARM 64 bit sched_clock take #2 Accept-Language: en-GB, en-US Content-Language: en-US User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephen, On Sat, Apr 20, 2013 at 01:29:02AM +0100, Stephen Boyd wrote: > This is what I was thinking. I don't see why we can't move this to generic > code and have arm64 use it too. Those patches will follow once I find an > arm64 compiler. > > First two patches should probably go in even if the 64 bit stuff doesn't go in > at the same time. > > Stephen Boyd (4): > ARM: sched_clock: Remove unused needs_suspend member > ARM: sched_clock: Return suspended count earlier > ARM: sched_clock: Add support for >32 bit sched_clock > ARM: arch_timer: Move to setup_sched_clock_64() > > arch/arm/include/asm/sched_clock.h | 5 +- > arch/arm/kernel/arch_timer.c | 14 +---- > arch/arm/kernel/sched_clock.c | 111 ++++++++++++++++++++++++++----------- > 3 files changed, 84 insertions(+), 46 deletions(-) I wanted to look at the series with more context, but I don't seem to be able to apply patch 2 and beyond to my tree, and I couldn't figure out what tree this series was based on. What do I need to use as the base for this series? Thanks, Mark. From mboxrd@z Thu Jan 1 00:00:00 1970 From: mark.rutland@arm.com (Mark Rutland) Date: Mon, 22 Apr 2013 16:34:08 +0100 Subject: [PATCH 0/4] ARM 64 bit sched_clock take #2 In-Reply-To: <1366417746-24990-1-git-send-email-sboyd@codeaurora.org> References: <51709FD7.8050408@gmail.com> <1366417746-24990-1-git-send-email-sboyd@codeaurora.org> Message-ID: <20130422153408.GD3791@e106331-lin.cambridge.arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Stephen, On Sat, Apr 20, 2013 at 01:29:02AM +0100, Stephen Boyd wrote: > This is what I was thinking. I don't see why we can't move this to generic > code and have arm64 use it too. Those patches will follow once I find an > arm64 compiler. > > First two patches should probably go in even if the 64 bit stuff doesn't go in > at the same time. > > Stephen Boyd (4): > ARM: sched_clock: Remove unused needs_suspend member > ARM: sched_clock: Return suspended count earlier > ARM: sched_clock: Add support for >32 bit sched_clock > ARM: arch_timer: Move to setup_sched_clock_64() > > arch/arm/include/asm/sched_clock.h | 5 +- > arch/arm/kernel/arch_timer.c | 14 +---- > arch/arm/kernel/sched_clock.c | 111 ++++++++++++++++++++++++++----------- > 3 files changed, 84 insertions(+), 46 deletions(-) I wanted to look at the series with more context, but I don't seem to be able to apply patch 2 and beyond to my tree, and I couldn't figure out what tree this series was based on. What do I need to use as the base for this series? Thanks, Mark.