From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Subject: Re: linux-next: Tree for December 3 Date: Thu, 03 Dec 2009 12:37:28 +0100 Message-ID: <4B17A2F8.9080408@petalogix.com> References: <20091203180214.16e452ed.sfr@canb.auug.org.au> <4B176B50.4050901@petalogix.com> <4B17771B.7050902@kernel.org> Reply-To: michal.simek@petalogix.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail-bw0-f227.google.com ([209.85.218.227]:62392 "EHLO mail-bw0-f227.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751053AbZLCLho (ORCPT ); Thu, 3 Dec 2009 06:37:44 -0500 In-Reply-To: <4B17771B.7050902@kernel.org> Sender: linux-next-owner@vger.kernel.org List-ID: To: Tejun Heo Cc: Stephen Rothwell , linux-next@vger.kernel.org, LKML Tejun Heo wrote: > Hello, > > On 12/03/2009 04:40 PM, Michal Simek wrote: >> todays tree is working on MMU microblaze correctly without any visible >> problem but noMMU microblaze kernel still have that bug as I reported >> some days ago. > > Other than triggering WARN_ON(), it doesn't cause any other problems, > right? It's probably because SMP_CACHE_BYTES on that configuration is > lower than 8. What is the value of SMP_CACHE_BYTES on the > configuration? Also, doesn't the Linus's tree have the same problem? aaa - I was too fast and compiled noMMU tree for 09-12-02 not todays. You can check it at http://www.monstr.eu/wiki/doku.php?id=log:log The problem seems to me is away. Thanks, Michal > > The somewhat spurious WARN_ON() in percpu allocator should probably be > just removed or bumped to check against PAGE_SIZE as SMP code does. > The problem is that on UP even though the function takes @align > parameter, it just ignores it. :-( > > Thanks. > -- Michal Simek, Ing. (M.Eng) PetaLogix - Linux Solutions for a Reconfigurable World w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663