From: Catalin Marinas <catalin.marinas@arm.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: "Martin MOKREJŠ" <mmokrejs@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.10.9: kmemleak disables all CPUs except CPU0
Date: Mon, 2 Sep 2013 16:48:40 +0100 [thread overview]
Message-ID: <20130902154840.GC13871@arm.com> (raw)
In-Reply-To: <CAMo8BfLMex3H1QBk6gD7DDDgGJ4dh6+dvhLG=c7LdFZ8XuyM9Q@mail.gmail.com>
On Mon, Sep 02, 2013 at 04:44:52PM +0100, Max Filippov wrote:
> On Mon, Sep 2, 2013 at 7:31 PM, Catalin Marinas <catalin.marinas@arm.com> wrote:
> > On 31 August 2013 14:35, Martin MOKREJŠ <mmokrejs@gmail.com> wrote:
> >> never realized that my CPUs are gone if I compile into kernel kmemleak.
> >> Is that really the aim?
> >>
> >> CONFIG_HAVE_DEBUG_KMEMLEAK=y
> >> CONFIG_DEBUG_KMEMLEAK=y
> >> CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=400
> >> # CONFIG_DEBUG_KMEMLEAK_TEST is not set
> >> # CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF is not set
> >>
> >> 1. Why isn't there /sys/devices/system/cpu/cpu0/online file?
> >> Does not matter if it contains 0 or 1. It just should exist.
> >
> > I can't really see how kmemleak would do this, maybe other config
> > options that get set/cleared in the process of selecting kmemleak. Can
>
> Seems to be kmemcheck: from arch/x86/mm/kmemcheck/kmemcheck.c:
>
> int __init kmemcheck_init(void)
> {
> #ifdef CONFIG_SMP
> /*
> * Limit SMP to use a single CPU. We rely on the fact that this code
> * runs before SMP is set up.
> */
> if (setup_max_cpus > 1) {
> printk(KERN_INFO
> "kmemcheck: Limiting number of CPUs to 1.\n");
> setup_max_cpus = 1;
> }
> #endif
Ah, ok, not my problem then ;)
--
Catalin
next prev parent reply other threads:[~2013-09-02 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 13:35 3.10.9: kmemleak disables all CPUs except CPU0 Martin MOKREJŠ
2013-09-02 15:31 ` Catalin Marinas
2013-09-02 15:44 ` Max Filippov
2013-09-02 15:48 ` Catalin Marinas [this message]
2013-09-02 15:51 ` Martin MOKREJŠ
2013-09-02 16:09 ` Catalin Marinas
2013-09-03 13:27 ` Martin MOKREJŠ
2013-09-02 15:46 ` Martin MOKREJŠ
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=20130902154840.GC13871@arm.com \
--to=catalin.marinas@arm.com \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmokrejs@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox