From: Robert Richter <robert.richter@cavium.com>
To: Hanjun Guo <hanjun.guo@linaro.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
<linux-arm-kernel@lists.infradead.org>, <will.deacon@arm.com>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<catalin.marinas@arm.com>, <akpm@linux-foundation.org>,
<xieyisheng1@huawei.com>, <james.morse@arm.com>
Subject: Re: [PATCH 2/2] arm64: mm: enable CONFIG_HOLES_IN_ZONE for NUMA
Date: Fri, 16 Dec 2016 18:14:06 +0100 [thread overview]
Message-ID: <20161216171406.GE4930@rric.localdomain> (raw)
In-Reply-To: <125f3064-bbec-d923-ad9f-b2d152ee2c2d@linaro.org>
On 16.12.16 09:57:20, Hanjun Guo wrote:
> Hi Robert,
>
> On 2016/12/15 23:39, Robert Richter wrote:
> >I was going to do some measurements but my kernel crashes now with a
> >page fault in efi_rtc_probe():
> >
> >[ 21.663393] Unable to handle kernel paging request at virtual address 20251000
> >[ 21.663396] pgd = ffff000009090000
> >[ 21.663401] [20251000] *pgd=0000010ffff90003
> >[ 21.663402] , *pud=0000010ffff90003
> >[ 21.663404] , *pmd=0000000fdc030003
> >[ 21.663405] , *pte=00e8832000250707
> >
> >The sparsemem config requires the whole section to be initialized.
> >Your patches do not address this.
>
> This patch set is running properly on D05, both the boot and
> LTP MM stress test are ok, seems it's a different configuration
> of memory mappings in firmware, just a stupid question, which
> part is related to this problem, is it only the Reserved memory?
The problem are efi reserved regions that are no longer reserved but
marked as nomap pages. Those are excluded from page initialization
causing parts of a memory section not being initialized.
-Robert
WARNING: multiple messages have this Message-ID (diff)
From: Robert Richter <robert.richter@cavium.com>
To: Hanjun Guo <hanjun.guo@linaro.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-arm-kernel@lists.infradead.org, will.deacon@arm.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
catalin.marinas@arm.com, akpm@linux-foundation.org,
xieyisheng1@huawei.com, james.morse@arm.com
Subject: Re: [PATCH 2/2] arm64: mm: enable CONFIG_HOLES_IN_ZONE for NUMA
Date: Fri, 16 Dec 2016 18:14:06 +0100 [thread overview]
Message-ID: <20161216171406.GE4930@rric.localdomain> (raw)
In-Reply-To: <125f3064-bbec-d923-ad9f-b2d152ee2c2d@linaro.org>
On 16.12.16 09:57:20, Hanjun Guo wrote:
> Hi Robert,
>
> On 2016/12/15 23:39, Robert Richter wrote:
> >I was going to do some measurements but my kernel crashes now with a
> >page fault in efi_rtc_probe():
> >
> >[ 21.663393] Unable to handle kernel paging request at virtual address 20251000
> >[ 21.663396] pgd = ffff000009090000
> >[ 21.663401] [20251000] *pgd=0000010ffff90003
> >[ 21.663402] , *pud=0000010ffff90003
> >[ 21.663404] , *pmd=0000000fdc030003
> >[ 21.663405] , *pte=00e8832000250707
> >
> >The sparsemem config requires the whole section to be initialized.
> >Your patches do not address this.
>
> This patch set is running properly on D05, both the boot and
> LTP MM stress test are ok, seems it's a different configuration
> of memory mappings in firmware, just a stupid question, which
> part is related to this problem, is it only the Reserved memory?
The problem are efi reserved regions that are no longer reserved but
marked as nomap pages. Those are excluded from page initialization
causing parts of a memory section not being initialized.
-Robert
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: robert.richter@cavium.com (Robert Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: mm: enable CONFIG_HOLES_IN_ZONE for NUMA
Date: Fri, 16 Dec 2016 18:14:06 +0100 [thread overview]
Message-ID: <20161216171406.GE4930@rric.localdomain> (raw)
In-Reply-To: <125f3064-bbec-d923-ad9f-b2d152ee2c2d@linaro.org>
On 16.12.16 09:57:20, Hanjun Guo wrote:
> Hi Robert,
>
> On 2016/12/15 23:39, Robert Richter wrote:
> >I was going to do some measurements but my kernel crashes now with a
> >page fault in efi_rtc_probe():
> >
> >[ 21.663393] Unable to handle kernel paging request at virtual address 20251000
> >[ 21.663396] pgd = ffff000009090000
> >[ 21.663401] [20251000] *pgd=0000010ffff90003
> >[ 21.663402] , *pud=0000010ffff90003
> >[ 21.663404] , *pmd=0000000fdc030003
> >[ 21.663405] , *pte=00e8832000250707
> >
> >The sparsemem config requires the whole section to be initialized.
> >Your patches do not address this.
>
> This patch set is running properly on D05, both the boot and
> LTP MM stress test are ok, seems it's a different configuration
> of memory mappings in firmware, just a stupid question, which
> part is related to this problem, is it only the Reserved memory?
The problem are efi reserved regions that are no longer reserved but
marked as nomap pages. Those are excluded from page initialization
causing parts of a memory section not being initialized.
-Robert
next prev parent reply other threads:[~2016-12-16 17:29 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 9:11 [PATCH 0/2] arm64: numa: fix spurious BUG() on NOMAP regions Ard Biesheuvel
2016-12-14 9:11 ` Ard Biesheuvel
2016-12-14 9:11 ` Ard Biesheuvel
2016-12-14 9:11 ` [PATCH 1/2] mm: don't dereference struct page fields of invalid pages Ard Biesheuvel
2016-12-14 9:11 ` Ard Biesheuvel
2016-12-14 9:11 ` Ard Biesheuvel
2017-01-04 12:16 ` Will Deacon
2017-01-04 12:16 ` Will Deacon
2017-01-04 12:16 ` Will Deacon
2016-12-14 9:11 ` [PATCH 2/2] arm64: mm: enable CONFIG_HOLES_IN_ZONE for NUMA Ard Biesheuvel
2016-12-14 9:11 ` Ard Biesheuvel
2016-12-14 9:11 ` Ard Biesheuvel
2016-12-15 15:39 ` Robert Richter
2016-12-15 15:39 ` Robert Richter
2016-12-15 15:39 ` Robert Richter
2016-12-15 16:07 ` Ard Biesheuvel
2016-12-15 16:07 ` Ard Biesheuvel
2016-12-15 16:07 ` Ard Biesheuvel
2016-12-16 17:10 ` Robert Richter
2016-12-16 17:10 ` Robert Richter
2016-12-16 17:10 ` Robert Richter
2016-12-16 1:57 ` Hanjun Guo
2016-12-16 1:57 ` Hanjun Guo
2016-12-16 1:57 ` Hanjun Guo
2016-12-16 17:14 ` Robert Richter [this message]
2016-12-16 17:14 ` Robert Richter
2016-12-16 17:14 ` Robert Richter
2017-01-04 13:28 ` Will Deacon
2017-01-04 13:28 ` Will Deacon
2017-01-04 13:28 ` Will Deacon
2017-01-04 13:50 ` Ard Biesheuvel
2017-01-04 13:50 ` Ard Biesheuvel
2017-01-04 13:50 ` Ard Biesheuvel
2017-01-04 14:02 ` Will Deacon
2017-01-04 14:02 ` Will Deacon
2017-01-04 14:02 ` Will Deacon
2017-01-05 11:24 ` Robert Richter
2017-01-05 11:24 ` Robert Richter
2017-01-05 11:24 ` Robert Richter
2017-01-05 12:08 ` Will Deacon
2017-01-05 12:08 ` Will Deacon
2017-01-05 12:08 ` Will Deacon
2017-01-05 12:22 ` Robert Richter
2017-01-05 12:22 ` Robert Richter
2017-01-05 12:22 ` Robert Richter
2017-01-05 19:49 ` Robert Richter
2017-01-05 19:49 ` Robert Richter
2017-01-05 19:49 ` Robert Richter
2017-01-06 12:03 ` Will Deacon
2017-01-06 12:03 ` Will Deacon
2017-01-06 12:03 ` Will Deacon
2017-01-06 12:22 ` Ard Biesheuvel
2017-01-06 12:22 ` Ard Biesheuvel
2017-01-06 12:22 ` Ard Biesheuvel
2017-02-06 13:36 ` Robert Richter
2017-02-06 13:36 ` Robert Richter
2017-02-06 13:36 ` Robert Richter
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=20161216171406.GE4930@rric.localdomain \
--to=robert.richter@cavium.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=hanjun.guo@linaro.org \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=will.deacon@arm.com \
--cc=xieyisheng1@huawei.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.