From: Laura Abbott <lauraa@codeaurora.org>
To: catalin.marinas@arm.com, mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-arm-msm@vger.kernel.org
Subject: [RFC PATCH] kmemleak: Add support for memory hotplug
Date: Tue, 15 Nov 2011 15:49:08 -0800 [thread overview]
Message-ID: <1321400949-1852-1-git-send-email-lauraa@codeaurora.org> (raw)
Currently, kmemleak is not supported with memory hotplug. This has
been discussed before[1] but never really went anywhere. Catalin's
other suggestion was to add callbacks for memory hotplug but given
there is now a nice lock_memory_hotplug function, this seems like
the right place to call it. Down the road call backs could be added
but this should hopefully enable hotplug to be used with kmemleak.
-Laura
[1] https://lkml.org/lkml/2010/3/22/395
next reply other threads:[~2011-11-15 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 23:49 Laura Abbott [this message]
2011-11-15 23:49 ` [RFC PATCH] kmemleak: Add support for memory hotplug Laura Abbott
2011-11-17 17:57 ` Catalin Marinas
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=1321400949-1852-1-git-send-email-lauraa@codeaurora.org \
--to=lauraa@codeaurora.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).