From: Scott Branden <scott.branden@broadcom.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] arm64: mm: add config options for page table configuration
Date: Fri, 9 Dec 2016 21:20:01 -0800 [thread overview]
Message-ID: <9c613ead-d215-3e53-40bf-126be3f1ad3e@broadcom.com> (raw)
In-Reply-To: <20161209105722.GD11767@arm.com>
Hi Will,
On 16-12-09 02:57 AM, Will Deacon wrote:
> On Thu, Dec 08, 2016 at 11:33:39AM -0800, Scott Branden wrote:
>> Since I currently have your attention: I do think there is fundamental bug
>> in the ARM64 mm implementation. If you look at /sys/devices/system/memory
>> it only shows the last memoryX section created after init.
>
> That directory doesn't seem to exist on my arm64 systems. Do I have to
> enable something specific in the .config?
I looked in the /sys/devices/system/memory at it doesn't look like it
appears until memory hotplug is enabled in the system. This is another
patch I'm trying to work through at the same time:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1284943.html
The internals of the memory management subsystem is not something I'm
too familiar with at this point.
>
> Will
>
Regards,
Scott
prev parent reply other threads:[~2016-12-10 5:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 19:39 [PATCH 0/1] " Scott Branden
2016-12-07 19:40 ` [PATCH 1/1] " Scott Branden
2016-12-08 10:00 ` Catalin Marinas
2016-12-08 16:30 ` Scott Branden
2016-12-08 18:57 ` Catalin Marinas
2016-12-08 19:33 ` Scott Branden
2016-12-09 10:57 ` Will Deacon
2016-12-10 5:20 ` Scott Branden [this message]
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=9c613ead-d215-3e53-40bf-126be3f1ad3e@broadcom.com \
--to=scott.branden@broadcom.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®