Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752568AbbKXBEq (ORCPT ); Mon, 23 Nov 2015 20:04:46 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:42820 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752364AbbKXBEo (ORCPT ); Mon, 23 Nov 2015 20:04:44 -0500 Date: Mon, 23 Nov 2015 17:04:42 -0800 From: Stephen Boyd To: Russell King - ARM Linux Cc: linux-arm-kernel@lists.infradead.org, =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= , Arnd Bergmann , Nicolas Pitre , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, Steven Rostedt Subject: Re: [RFC/PATCH 2/3] recordmcount: Record locations of __aeabi_{u}idiv() calls on ARM Message-ID: <20151124010442.GP19156@codeaurora.org> References: <1448068997-26631-1-git-send-email-sboyd@codeaurora.org> <1448068997-26631-3-git-send-email-sboyd@codeaurora.org> <20151121101349.GI8644@n2100.arm.linux.org.uk> <20151123205335.GD19156@codeaurora.org> <20151123210347.GW8644@n2100.arm.linux.org.uk> <20151123211601.GE19156@codeaurora.org> <20151123213337.GX8644@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151123213337.GX8644@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1177 Lines: 31 On 11/23, Russell King - ARM Linux wrote: > On Mon, Nov 23, 2015 at 01:16:01PM -0800, Stephen Boyd wrote: > > Thanks. I don't see the prints on my system even with this config > > on top of allyesconfig. Odd. > > Hmm. > > It could be because I use ccache in hardlink mode to avoid the disk > overhead of having two copies and having to duplicate the file > contents. > > If the kernel build thinks it can modify an object file in place, it > will lead to this, as it will end up modifying the stored ccache > file unless it specifically breaks the hardlink. > That sounds very possible. I'd have to get ccache setup with hardlinks to test out your theory. Is it supported to use ccache with hardlinks to build the kernel? The ccache documentation makes it sounds like it will confuse make and isn't a good idea. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- 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/