On 2017/11/14 0:54, Thomas Gleixner wrote:
> On Wed, 8 Nov 2017, Zhenzhong Duan wrote:
>
>> There is no way a timer used as broadcast clockevent device is also used as
>> percpu tick clockevent device currently.
> Correct.
>
>> It's better to put related code in tick_install_broadcast_device(), but I feel
>> it's harmless to give it back to the clockevents layer. Pls correct me if I'm
>> wrong.
> You already established, that it _cannot_ be the broadcast device and the
> per cpu device at the same time. So that condition can never be true. What
> do you want to put into tick_install_broadcast_device()? This second
> paragraph doesn't make sense, unless I'm missing something.
I didn't find the reason in long history logs while the comments saying 'If the current device is the broadcast device, do not give it back to the clockevents layer !'
If it does, tick_install_broadcast_device() is a proper place. If not, I can resend the patch with fresh description, pls confirm.
--
thanks
zduan
From 1583970652159949644@xxx Mon Nov 13 16:55:28 +0000 2017
X-GM-THRID: 1583562997246093706
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread