Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965041AbdCWVRc (ORCPT ); Thu, 23 Mar 2017 17:17:32 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:35024 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752070AbdCWVRb (ORCPT ); Thu, 23 Mar 2017 17:17:31 -0400 Date: Thu, 23 Mar 2017 22:17:24 +0100 (CET) From: Thomas Gleixner To: Nicolas Pitre cc: Daniel Lezcano , linux-kernel@vger.kernel.org, peterz@infradead.org, rafael@kernel.org, vincent.guittot@linaro.org Subject: Re: [PATCH V8 2/3] irq: Track the interrupt timings In-Reply-To: Message-ID: References: <1490290924-12958-1-git-send-email-daniel.lezcano@linaro.org> <1490290924-12958-2-git-send-email-daniel.lezcano@linaro.org> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 331 Lines: 14 On Thu, 23 Mar 2017, Nicolas Pitre wrote: > Is there a need for 64 bits of relative time stamps? > And 32 bits of IRQ number? No. > I'd say that 48 bit time stamp and 16 bit IRQ number is way sufficient. > Who cares if we mispredict an IRQ after 78 hours of idle time? > > Hence: > > u64 value = (ts << 16) | irq; Excellent!