Message-ID: <1491291123.4294.28.camel@gmx.de>
Subject: Re: [BUG nohz]: wrong user and system time accounting
From: Mike Galbraith <efault@gmx.de>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Rik van Riel <riel@redhat.com>,
        Luiz Capitulino <lcapitulino@redhat.com>,
        Wanpeng Li <kernellwp@gmail.com>, linux-kernel@vger.kernel.org
Date: Tue, 04 Apr 2017 09:32:03 +0200
In-Reply-To: <20170403144047.GA3820@lerouge>
References: <20170323165512.60945ac6@redhat.com>
         <CANRm+CxcgSP2-x+A822DmHLvFLzFmTptS6oYwYtwVdErTpiB=Q@mail.gmail.com>
         <1490636129.8850.76.camel@redhat.com> <20170328132406.7d23579c@redhat.com>
         <20170329131656.1d6cb743@redhat.com> <1490818125.28917.11.camel@redhat.com>
         <1490848051.4167.57.camel@gmx.de> <20170330125157.GB3626@lerouge>
         <1490878951.28917.16.camel@redhat.com> <1490880922.4702.66.camel@gmx.de>
         <20170403144047.GA3820@lerouge>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 339
Lines: 7

On Mon, 2017-04-03 at 16:40 +0200, Frederic Weisbecker wrote:
> On Thu, Mar 30, 2017 at 03:35:22PM +0200, Mike Galbraith wrote:

> Nohz_full is already bad for powersavings anyway. CPU 0 always ticks :-)

OTOH, if a nohz_full set is doing what it was born to do, CPU0 tick
spikes won't be noticeable on your (pegged/glowing) watt meter :)