From: Dave Hansen <dave.hansen@intel.com>
To: Alexander Duyck <alexander.duyck@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: alexander.h.duyck@intel.com, pavel.tatashin@microsoft.com,
mhocko@suse.com, akpm@linux-foundation.org, mingo@kernel.org,
kirill.shutemov@linux.intel.com
Subject: Re: [PATCH v2 1/2] mm: Move page struct poisoning to CONFIG_DEBUG_VM_PAGE_INIT_POISON
Date: Wed, 5 Sep 2018 14:34:20 -0700 [thread overview]
Message-ID: <185e6fb5-f247-bba2-e082-c3097e78fc04@intel.com> (raw)
In-Reply-To: <20180905211328.3286.71674.stgit@localhost.localdomain>
On 09/05/2018 02:13 PM, Alexander Duyck wrote:
> Instead of keeping the value in CONFIG_DEBUG_VM I am adding a new CONFIG
> value called CONFIG_DEBUG_VM_PAGE_INIT_POISON that will control the page
> poisoning independent of the CONFIG_DEBUG_VM option.
I guess this is a reasonable compromise.
If folks see odd 'struct page' corruption, they'll have to know to go
turn this on and reboot, though.
next prev parent reply other threads:[~2018-09-05 21:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 21:13 [PATCH v2 0/2] Address issues slowing memory init Alexander Duyck
2018-09-05 21:13 ` [PATCH v2 1/2] mm: Move page struct poisoning to CONFIG_DEBUG_VM_PAGE_INIT_POISON Alexander Duyck
2018-09-05 21:22 ` Pasha Tatashin
2018-09-05 21:29 ` Alexander Duyck
2018-09-05 21:38 ` Pasha Tatashin
2018-09-05 21:54 ` Alexander Duyck
2018-09-05 21:34 ` Dave Hansen [this message]
2018-09-06 5:47 ` Michal Hocko
2018-09-06 14:59 ` Dave Hansen
2018-09-06 15:13 ` Michal Hocko
2018-09-06 15:41 ` Alexander Duyck
2018-09-06 16:12 ` Pasha Tatashin
2018-09-06 17:07 ` Dave Hansen
2018-09-06 18:08 ` Michal Hocko
2018-09-06 17:03 ` Michal Hocko
2018-09-06 17:23 ` Pasha Tatashin
2018-09-06 16:09 ` Dave Hansen
2018-09-06 17:08 ` Michal Hocko
2018-09-05 21:13 ` [PATCH v2 2/2] mm: Create non-atomic version of SetPageReserved for init use Alexander Duyck
2018-09-06 5:49 ` Michal Hocko
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=185e6fb5-f247-bba2-e082-c3097e78fc04@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=pavel.tatashin@microsoft.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