From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: kasan: print memory assignment
Date: Tue, 26 May 2015 10:44:26 +0100 [thread overview]
Message-ID: <20150526094425.GD1565@arm.com> (raw)
In-Reply-To: <1432632464-12248-1-git-send-email-linus.walleij@linaro.org>
On Tue, May 26, 2015 at 10:27:44AM +0100, Linus Walleij wrote:
> This prints out the virtual memory assigned to KASan in the
> boot crawl along with other memory assignments, if and only
> if KASan is activated.
>
> Example dmesg from the Juno Development board:
>
> Memory: 1691156K/2080768K available (5465K kernel code, 444K rwdata,
> 2160K rodata, 340K init, 217K bss, 373228K reserved, 16384K cma-reserved)
> Virtual kernel memory layout:
> kasan : 0xffffff8000000000 - 0xffffff9000000000 ( 64 MB)
Unfortunately, that's a *lot* bigger than 64MB!
Will
next prev parent reply other threads:[~2015-05-26 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 9:27 [PATCH] ARM64: kasan: print memory assignment Linus Walleij
2015-05-26 9:44 ` Will Deacon [this message]
2015-05-26 13:36 ` Linus Walleij
2015-05-26 13:13 ` Andrey Ryabinin
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=20150526094425.GD1565@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).