From: Tejun Heo <tj@kernel.org>
To: michal.simek@petalogix.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 3
Date: Thu, 03 Dec 2009 17:30:19 +0900 [thread overview]
Message-ID: <4B17771B.7050902@kernel.org> (raw)
In-Reply-To: <4B176B50.4050901@petalogix.com>
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?
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.
--
tejun
next prev parent reply other threads:[~2009-12-03 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 7:02 linux-next: Tree for December 3 Stephen Rothwell
2009-12-03 7:40 ` Michal Simek
2009-12-03 8:30 ` Tejun Heo [this message]
2009-12-03 11:37 ` Michal Simek
2009-12-03 13:37 ` Jiri Kosina
2009-12-03 14:13 ` Stephen Rothwell
2009-12-03 14:18 ` Jiri Kosina
-- strict thread matches above, loose matches on Subject: below --
2010-12-03 2:04 Stephen Rothwell
2008-12-03 7:36 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B17771B.7050902@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=michal.simek@petalogix.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox