From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D8AEBC4707F for ; Thu, 27 May 2021 11:56:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B24FE60FDC for ; Thu, 27 May 2021 11:56:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234406AbhE0L61 (ORCPT ); Thu, 27 May 2021 07:58:27 -0400 Received: from mail.kernel.org ([198.145.29.99]:50030 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234393AbhE0L6Y (ORCPT ); Thu, 27 May 2021 07:58:24 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 1F49760FDC; Thu, 27 May 2021 11:56:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1622116612; bh=u54942qCqCDChWDp0gmC+kIls65S7seqXb/ejFgySWY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pUVHMJEaWagk+WzBsErjHIj4FJAMx2ppZ237lTS8wRsbb5Yh7FGPWfFMvRiS9lrO0 yobgqGFkHA+jnYcGtqQx4fyyK0U0glwA5TGGZOtF/DtlLDDpyLN4G2LHgtrpGUplaM 7u+uYs+VOJlPTu+IScVjHQV+O/YtEbNqjxHjTIkX10jbS174hQmWJ7m+ioekg3zbkz FRP8v5PwS3+4GdCAgiGLZLZ9doZJOtBze7bb62zZb37vBk+X+xcEqeqZbKE52RXROd JS2ZVLYeu2hYo02rN4TUBYwA1s0YHciZepS4gzWTw4e2ftv92PY4kJLNFGNG+e9ipB I7wqX1KOCIZdA== Date: Thu, 27 May 2021 12:56:46 +0100 From: Will Deacon To: Xin Hao Cc: fweisbec@gmail.com, john.stultz@linaro.org, kernel-team@android.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, lorenzo@google.com, maz@kernel.org, mika.penttila@nextfour.com, sboyd@kernel.org, tglx@linutronix.de Subject: Re: [PATCH v2 2/5] tick/broadcast: Split __tick_broadcast_oneshot_control() into a helper Message-ID: <20210527115646.GD22019@willie-the-truck> References: <20210524221818.15850-3-will@kernel.org> <20210527082219.GA21311@willie-the-truck> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 27, 2021 at 07:35:03PM +0800, Xin Hao wrote: > > 在 2021/5/27 下午4:22, Will Deacon 写道: > > On Thu, May 27, 2021 at 03:23:06PM +0800, Xin Hao wrote: > > >      I  had backport you  tick/broadcast: Prefer per-cpu relatives patches, > > > > > > but i did not get the true result,  the Wakeup Devices are all null, why? > > Probably because you don't have any suitable per-cpu timers to act as a > > wakeup. Do you have a per-cpu timer registered with CLOCK_EVT_FEAT_PERCPU > > Yes, you are right, but i want to know why the timer do not support  > CLOCK_EVT_FEAT_PERCPU. I defer to Thomas on this one. The approach I have taken here (of printing ) follows what is done elsewhere for the timer readout and probably helps with parsing this stuff. Will