From: Russell King <rmk@arm.linux.org.uk>
To: ShiYong LI <a22381@motorola.com>
Cc: Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Shiyong Li <shi-yong.li@motorola.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
David Rientjes <rientjes@google.com>
Subject: Re: "slab: Fix missing DEBUG_SLAB last user" breaks ARM
Date: Mon, 14 Feb 2011 15:40:12 +0000 [thread overview]
Message-ID: <20110214154011.GA1595@flint.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTimDUf52xdHn22=f1J=Xn88sqPEg9P6+ceas1h1k@mail.gmail.com>
On Mon, Feb 14, 2011 at 11:10:45AM +0800, ShiYong LI wrote:
> Hi all,
>
> Sorry for my late reply.
>
> My commit is created to enable ARM with 128 byte cache line support last
> information dump while slab corruption occurs. I've verified it works fine
> on ARMv7.
Mainline only supports 32 byte and 64 byte cache lines on ARM. It does
not support 128 byte cache lines, so maybe your attempts are the wrong
approach. Can you please post your 128 byte cache line support patches
to the ARM kernel mailing list for review.
In the mean time, because your patch causes an oopsing regression, I
strongly suggest that it is reverted until we start supporting 128 byte
cache lines on ARM in mainline.
> Russell,
>
> Can you provide more information for the problem? What kind of ARM are you
> using ?
ARM926, which has a cache line size of 32.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2011-02-14 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 18:06 "slab: Fix missing DEBUG_SLAB last user" breaks ARM Russell King
2011-02-08 5:44 ` Pekka Enberg
2011-02-08 12:55 ` Russell King
2011-02-08 15:02 ` Christoph Lameter
2011-02-11 7:02 ` Pekka Enberg
2011-02-11 9:14 ` Russell King
2011-02-11 15:20 ` Christoph Lameter
2011-02-11 15:35 ` Russell King
[not found] ` <AANLkTimDUf52xdHn22=f1J=Xn88sqPEg9P6+ceas1h1k@mail.gmail.com>
2011-02-14 15:40 ` Russell King [this message]
2011-02-14 15:43 ` Pekka Enberg
2011-02-14 18:07 ` Pekka Enberg
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=20110214154011.GA1595@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=a22381@motorola.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=shi-yong.li@motorola.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.