Date: Thu, 16 Jul 2015 01:34:19 +0100
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: linux-kernel@vger.kernel.org, Jeff Epler <jepler@unpythonic.net>,
        =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker <fweisbec@gmail.com>,
        Rik van Riel <riel@redhat.com>
Subject: Re: CONFIG_NO_HZ_FULL restricts cpu usage to the equivalent of one
 in 4.2
Message-ID: <20150716003419.GB15221@milliways>
References: <20150715162713.GA29360@milliways>
 <55A6AEE1.4080109@amacapital.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <55A6AEE1.4080109@amacapital.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 776
Lines: 21

On Wed, Jul 15, 2015 at 12:05:05PM -0700, Andy Lutomirski wrote:
> 
> Before going nuts bisecting, it could be worth running perf record -a -g -e
> cycles (or perhaps -e task-clock instead of -e cycles).  It could also be
> worth manually sampling /proc/PID/stack a few times for a process that isn't
> making as much progress as it should.
> 
> --Andy

I think Frederic has already spotted the problem - in the early
bisects, everything was building on CPU 0.  But thanks for the
suggestion.

ĸen
-- 
This one goes up to eleven!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/