Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp3617787imm; Sun, 16 Sep 2018 23:38:01 -0700 (PDT) X-Google-Smtp-Source: ANB0Vda1yXuo7eNUzsjCFGXKa9OLIGuzvVnqGB9qQv6cdlWfcclw72tQvjbqErTtc1owDWhCi9oK X-Received: by 2002:a17:902:9893:: with SMTP id s19-v6mr23465207plp.130.1537166281620; Sun, 16 Sep 2018 23:38:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537166281; cv=none; d=google.com; s=arc-20160816; b=r/fYiBMv5CEh/xj0enT4WNR5cNT0wzxE13ofWY7fioDw1+QctBQQV6VympbNFcqjPR L1LzcMeNnccyKCdjY4o4pgkeCC3RxnTferl6+hAKAS6epHnyfKmv+X+5eJDi2dZyYL4F M1L8QqJbuWMiqyzUAjiVaIAkL1ZtoAcLbvdU1WtGjS34p2TD4RYt+eCGPLVxsHBOupi+ nrM6lrGB2SZ/YEbMKRz8FPprbabq71BrfR2cibczwaeh/8TbhYKleZ4TiK+pIXstl/b/ Ti8s3dyfU1UVKdDQ2N9o0FqCRikjcf0OzaA2qHIt51eaPS6wsqwz9RAvL5hQj4huBX2p sWHA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:from:subject; bh=C49nnT3PMUpyZbpKnWfgdivUbNjqXv1oYR7UPTseJTc=; b=kUIT5dCwhHSjr3gvNAhzyqIpu71ocIwl+Chk/X4z60Ag+occu9jVZvFbUMj3BCRdF0 VXzBAPgYV2p0PtgKJltukBEGNfcwT+pPQDwO/fvikp4gOSnOOto7L+YcSyuoY0WVPy8Q lSUrt+xHggTGj0PnQzcwP+WSwmVbJdxW2YX8EoHTs2jnzbl+5gUDQx79LBZxb/0cNJ6h wKXzK21/kFLQYDet0Z3xQjT9DSr8VB+Plxrq+ecjvEXTVoMR5cBfWStT7OSbN1d8Ba1+ ZGq51c2P9J/+mpqOLp1v9dEJXsCTRSSZ0BNG90zX3k7OLlRfz3voBP8+Uc+nrerSanPl irUw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t15-v6si14521818pgq.365.2018.09.16.23.37.46; Sun, 16 Sep 2018 23:38:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728360AbeIQMD2 (ORCPT + 99 others); Mon, 17 Sep 2018 08:03:28 -0400 Received: from lizzard.sbs.de ([194.138.37.39]:41646 "EHLO lizzard.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727440AbeIQMD2 (ORCPT ); Mon, 17 Sep 2018 08:03:28 -0400 X-Greylist: delayed 796 seconds by postgrey-1.27 at vger.kernel.org; Mon, 17 Sep 2018 08:03:27 EDT Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id w8H6NRpQ009070 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 17 Sep 2018 08:23:27 +0200 Received: from [139.22.44.236] ([139.22.44.236]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id w8H6NR3Z012693; Mon, 17 Sep 2018 08:23:27 +0200 Subject: Re: [PATCH] arm: Initialize hrtimer-based broadcast clockevent From: Jan Kiszka To: Russell King , linux-arm-kernel , Thomas Gleixner , Arnd Bergmann Cc: Jailhouse , Linux Kernel Mailing List References: <86a7e675-11bd-3b8b-22a0-8f440db96293@siemens.com> <8f2fd3b9-416a-992e-5ca6-fc83aad5700d@siemens.com> <35966a15-8312-5ba9-ef76-33a6cfda1f32@siemens.com> Message-ID: Date: Mon, 17 Sep 2018 08:23:26 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11.06.18 07:42, Jan Kiszka wrote: > On 2018-04-04 17:54, Jan Kiszka wrote: >> On 2018-03-01 07:04, Jan Kiszka wrote: >>> On 2018-01-22 07:06, Jan Kiszka wrote: >>>> Analogously to 9358d755bd5c, this registers a broadcast clockevent in >>>> case no hardware broadcast timer is available and the per-CPU timers can >>>> be stopped in deep power states. >>>> >>>> Partitions of the Jailhouse hypervisor fall in this category. >>>> Registering the workaround timer allows to enter high-resolution mode in >>>> that case. >>>> >>>> Signed-off-by: Jan Kiszka >>>> --- >>>> arch/arm/kernel/time.c | 3 +++ >>>> 1 file changed, 3 insertions(+) >>>> >>>> diff --git a/arch/arm/kernel/time.c b/arch/arm/kernel/time.c >>>> index 629f8e9981f1..0a45d861ef8e 100644 >>>> --- a/arch/arm/kernel/time.c >>>> +++ b/arch/arm/kernel/time.c >>>> @@ -12,6 +12,7 @@ >>>> * reading the RTC at bootup, etc... >>>> */ >>>> #include >>>> +#include >>>> #include >>>> #include >>>> #include >>>> @@ -121,5 +122,7 @@ void __init time_init(void) >>>> of_clk_init(NULL); >>>> #endif >>>> timer_probe(); >>>> + >>>> + tick_setup_hrtimer_broadcast(); >>>> } >>>> } >>>> >>> >>> Gentle ping, just to avoid that this falls through the cracks because >>> it's so small. >>> >> >> 2nd ping. Should this patch be routed via ARM or rather some tip/timers >> tree? >> > > 3rd try: Could someone have a look at this and merge it - or at least > ack it in order to move forward? > Still no reactions, so I'm kindly reminding of this patch again. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux