Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752519AbdIAVWL (ORCPT ); Fri, 1 Sep 2017 17:22:11 -0400 Received: from semf07.mfg.siteprotect.com ([64.26.60.170]:39100 "EHLO semf07.mfg.siteprotect.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752392AbdIAVWJ (ORCPT ); Fri, 1 Sep 2017 17:22:09 -0400 X-Greylist: delayed 1035 seconds by postgrey-1.27 at vger.kernel.org; Fri, 01 Sep 2017 17:22:09 EDT Date: Fri, 1 Sep 2017 17:03:52 -0400 (EDT) From: Vince Weaver X-X-Sender: vince@pianoman.cluster.toy To: Peter Zijlstra cc: Alexey Budankov , Ingo Molnar , Arnaldo Carvalho de Melo , Alexander Shishkin , Andi Kleen , Kan Liang , Dmitri Prokhorov , Valery Cherepennikov , Mark Rutland , Stephane Eranian , David Carrillo-Cisneros , linux-kernel , Thomas Gleixner Subject: Re: [RFC][PATCH] perf: Rewrite enabled/running timekeeping In-Reply-To: <20170831171837.njnc6r6elsvkl7lt@hirez.programming.kicks-ass.net> Message-ID: References: <96c7776f-1f17-a39e-23e9-658596216d6b@linux.intel.com> <20170803150052.za2vofyqfgarukdr@hirez.programming.kicks-ass.net> <20170822204743.GR32112@worktop.programming.kicks-ass.net> <2a426aa2-42c8-e839-1cec-aa3971651f3e@linux.intel.com> <20170831171837.njnc6r6elsvkl7lt@hirez.programming.kicks-ass.net> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Originating-IP: 64.26.60.147 X-SpamExperts-Domain: hostwaytestmfg.com X-SpamExperts-Username: 64.26.60.144/30 Authentication-Results: mfg.siteprotect.com; auth=pass smtp.auth=64.26.60.144/30@hostwaytestmfg.com X-SpamExperts-Outgoing-Class: ham X-SpamExperts-Outgoing-Evidence: SB/global_tokens (0.000259389812776) X-Recommended-Action: accept X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZiISEN1Ocf8i9ROgg9Mirrhj3F7O0axxCVd UC3Xh80jAIsEMysPur9wmiDBurOy6iR7LQbkVGtsvndukEo8d8CbxDM3qyX0GvVAGCrIBFfKfuub KDu41/FW2XC6vZZtdlxS9+CgTtPHw9ghx6Q63LlXHJkdjadwxzKV4qIbOGwJPGnHI/MButNh7rg7 qdQJC1t4Yg06hiBmyQ3tGy4q5SDhPAlbDjazCbhs7qBpykynMjuWD70g97tK3xetVePZtK1MyPa0 CqHwcyLbRvzzj2L8U6KmwZKOnfGsQeToOdoWXrl68J6NLkbF5fv7vfHdhcKpd4ukuMkJXStBmgUG pdnwoN/4COfehEPQulC3qQbMoXc5UMNNeMIajcifL+N17r6dpdd2qOBdSt1kEczBnJ7P4pWx7WxW FZpsjT/483ewgpFb9zIn21xx2x3C2o4G69gSp1r7yMKvousW7u2JkIblpxE+qxXzCoEav5vkZRW1 y05dSbp8eJkFZFXOAfhzbo/3D4gJSHYyaxNPOkwkaAerHY7bsEqEtQl+qBJaWxUUs5FJSOwVjw2/ ywHvy96C29SDwIE7VKe+bqpcdCns72R1NPJnGZdzosokZOVOJN4PXM/eXmgiC8MfWFoLjMHg3e/6 MH9nVbUMNE0cZAZhjREcMP/mYplPjeH759OF5aMdZJs9zSZic0xNU+sMoNUh1wsDUceqCWhlSNvZ OgQyUmcHwAmx5+1bvKRQKugQE6IWFXeiCDelFPfPHvfZbkYHtkiegmXDkimaujU7JC0W3dwLDaRB dAL1sU+RoGRlbf9rNAJd4Kc2LYyasmDRrWNMAxpkAdhK23InA2zzja5I1riD9P+dAgNwsD40O65S MCgE14jEq0C65IKmzfapDMpurD+kU8WJwg1wIkgsgsEjmmIz4qTO/bNcQTdv5Ijzh2LeGsvzZyX+ w4ZJOf5WuVJQaJNtsJ5jRcvYQuJ/ta6UVOJ/TR8dtByWYYhgj25jR+mEA7Rgp6uiPLC3zh9HdutF ia8qv93xSWEaK7bk5zCe95RPdib6j469Fx9dL8AS7kNqtVvLDs9D1fg9cHtwdmw7NkSYZtwFVsLW rFklrq2if+MXkQjJI8EJGcuHARkoKDqq7mzMX/UyZu7Y75yvv3JgMqpUC7b07Pj2L/DtBVUieqCh nOQIaJWXdIN8hiA+RQzpyIo9Qe7Hvc0FT5/ZCH/KhW0JXtK9fRK1CP3x88vYpZESvYhAggUrOtcW NYnS2NSUwgmqQ/WeQXO5Xnh6QMGY5mGYBOp4w/g6wv5YjPltQS3QuMZdfmk/cjqwaq6VDbK0t+yi La091Ptg9kiqm4QCjfB8LN00Y2guNhbTSbk1sIe8wvzGFXyg+e1KC/iyjQbxCg== X-Report-Abuse-To: spam@semfq02.mfg.siteprotect.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 927 Lines: 24 On Thu, 31 Aug 2017, Peter Zijlstra wrote: > So the below completely rewrites timekeeping (and probably breaks > world) but does away with the need to touch events that don't get > scheduled. > > Esp the cgroup stuff is entirely untested since I simply don't know how > to operate that. I did run Vince's tests on it, and I think it doesn't > regress, but I'm near a migraine so I can't really see straight atm. > > Vince, Stephane, could you guys have a peek? I have to admit that I *always* got lost trying to figure out the old so I might not be the best person to review the changes. I did try running the perf_event_tests on a few machines and they all pass. I also ran the PAPI tests and a few of the multiplexing tests fail about 10% of the time but I think they also fail 10% of the time with the old code too. I need to figure out why that's happening but it's likely a PAPI issue not a kernel one. Vince