From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752212AbbCSJiQ (ORCPT <rfc822;w@1wt.eu>);
	Thu, 19 Mar 2015 05:38:16 -0400
Received: from casper.infradead.org ([85.118.1.10]:59854 "EHLO
	casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750860AbbCSJiI (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 19 Mar 2015 05:38:08 -0400
Message-Id: <20150319093137.149794496@infradead.org>
User-Agent: quilt/0.61-1
Date: Thu, 19 Mar 2015 10:31:37 +0100
From: Peter Zijlstra <peterz@infradead.org>
To: john.stultz@linaro.org, tglx@linutronix.de
Cc: pawel.moll@arm.com, adrian.hunter@intel.com, mingo@kernel.org,
        eranian@google.com, linux-kernel@vger.kernel.org, acme@kernel.org,
        dsahern@gmail.com, fweisbec@gmail.com, jolsa@redhat.com,
        namhyung@gmail.com, paulus@samba.org, rostedt@goodmis.org,
        sonnyrao@chromium.org, ak@linux.intel.com, vincent.weaver@maine.edu,
        peterz@infradead.org
Subject: [RFC][PATCH 0/4] Another go at ktime_get_raw_fast_ns()
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi John,

So yeah, I just didn't try hard enough it seems; how about this?

Also, I think we should double check that everything passed to
tk_setup_internals(.clock) is either static storage or RCU-sched freed,
because with the whole latch thing one CPUs (fast) access might still be
in progress while the other is freeing the clock struct.

Not sure what the lifetime rules of struct clocksource are here.