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 S1760115AbbKTTLx (ORCPT <rfc822;w@1wt.eu>);
	Fri, 20 Nov 2015 14:11:53 -0500
Received: from mail-io0-f173.google.com ([209.85.223.173]:34646 "EHLO
	mail-io0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751471AbbKTTLw (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 20 Nov 2015 14:11:52 -0500
MIME-Version: 1.0
In-Reply-To: <564F6A92.7080006@arm.com>
References: <1448027861-21472-1-git-send-email-grygorii.strashko@ti.com>
	<564F570C.7030409@oracle.com>
	<564F67ED.9000905@ti.com>
	<564F6A92.7080006@arm.com>
Date: Fri, 20 Nov 2015 11:11:51 -0800
Message-ID: <CALAqxLVMtL+Vkao1i61zQFzcPK3VE3ZtUyu1B1TuPQppOGcUNQ@mail.gmail.com>
Subject: Re: [PATCH v2] clocksource: arm_global_timer: fix suspend resume
From: John Stultz <john.stultz@linaro.org>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
        santosh shilimkar <santosh.shilimkar@oracle.com>,
        Russell King - ARM Linux <linux@arm.linux.org.uk>,
        Daniel Lezcano <daniel.lezcano@linaro.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Srinivas Kandagatla <srinivas.kandagatla@gmail.com>,
        Maxime Coquelin <maxime.coquelin@st.com>,
        lkml <linux-kernel@vger.kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
        kernel@stlinux.com,
        "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
        Arnd Bergmann <arnd@arndb.de>, Felipe Balbi <balbi@ti.com>,
        Tony Lindgren <tony@atomide.com>,
        Santosh Shilimkar <ssantosh@kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Nov 20, 2015 at 10:46 AM, Marc Zyngier <marc.zyngier@arm.com> wrote:
>
> This patch has a very specific purpose: instructing the core code that
> this timer will never stop ticking, ever. It is really targeted at
> virtual machines, whose timer is backed by the host timer, even when the
> VM is not running.
>
> Using it on actual hardware is may not be the best idea, specially in
> the presence of PM.

And actually, the CLOCK_SOURCE_SUSPEND_NONSTOP flag was added to
support real hardware, so its not just limited to VMs. But that
hardware does have to keep the lights on for the counter backing the
clocksource, and I'm not sure how common it ever became.

thanks
-john