From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752248AbbAKMlw (ORCPT ); Sun, 11 Jan 2015 07:41:52 -0500 Received: from mail-we0-f180.google.com ([74.125.82.180]:64409 "EHLO mail-we0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750922AbbAKMlv (ORCPT ); Sun, 11 Jan 2015 07:41:51 -0500 Date: Sun, 11 Jan 2015 13:41:46 +0100 From: Richard Cochran To: John Stultz Cc: Linux Kernel Mailing List , Dave Jones , Linus Torvalds , Thomas Gleixner , Prarit Bhargava , Stephen Boyd , Ingo Molnar , Peter Zijlstra Subject: Re: [PATCH 06/10] time: Cap clocksource reads to the clocksource max_cycles value Message-ID: <20150111124146.GA15387@localhost.localdomain> References: <1420850068-27828-1-git-send-email-john.stultz@linaro.org> <1420850068-27828-7-git-send-email-john.stultz@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1420850068-27828-7-git-send-email-john.stultz@linaro.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 09, 2015 at 04:34:24PM -0800, John Stultz wrote: > When calculating the current delta since the last tick, we > currently have no hard protections to prevent a multiplciation > overflow from ocurring. This is just papering over the problem. The "hard protection" should be having a tick scheduled before the range of the clock source is exhausted. Thanks, Richard