From: Simon Jeons <simon.jeons@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Minchan Kim <minchan@kernel.org>,
Sasha Levin <sasha.levin@oracle.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Mel Gorman <mgorman@suse.de>, Dave Jones <davej@redhat.com>,
linux-mm <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: mm: BUG in do_huge_pmd_wp_page
Date: Thu, 25 Apr 2013 07:40:02 +0800 [thread overview]
Message-ID: <51786D52.1080509@gmail.com> (raw)
In-Reply-To: <517861E0.7030801@zytor.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Hi Peter,
On 04/25/2013 06:51 AM, H. Peter Anvin wrote:
> On 04/10/2013 01:02 AM, Minchan Kim wrote:
>> When I am looking at the code, I was wonder about the logic of GHZP(aka,
>> get_huge_zero_page) reference handling. The logic depends on that page
>> allocator never alocate PFN 0.
>>
>> Who makes sure it? What happens if allocator allocates PFN 0?
>> I don't know all of architecture makes sure it.
>> You investigated it for all arches?
>>
> This isn't manifest, right? At least on x86 we should never, ever
> allocate PFN 0.
I see in memblock_trim_memory(): start = round_up(orig_start, align);
here align is PAGE_SIZE, so the dump of zone ranges in my machine is [
0.000000] DMA [mem 0x00001000-0x00ffffff]. Why PFN 0 is not
used? just for align?
>
> -hpa
>
>
> --
> 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>
[-- Attachment #2: Type: text/html, Size: 2514 bytes --]
next prev parent reply other threads:[~2013-04-24 23:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 13:04 mm: BUG in do_huge_pmd_wp_page Sasha Levin
2013-04-04 14:03 ` Sasha Levin
2013-04-04 14:30 ` Kirill A. Shutemov
2013-04-04 14:37 ` Sasha Levin
2013-04-04 16:28 ` Kirill A. Shutemov
2013-04-04 21:54 ` Sasha Levin
2014-04-04 19:37 ` Sasha Levin
2014-04-07 14:48 ` Kirill A. Shutemov
2014-04-07 14:56 ` Sasha Levin
2014-04-07 19:40 ` Sasha Levin
2014-04-07 20:11 ` Kirill A. Shutemov
2014-05-15 17:31 ` Sasha Levin
2014-05-15 17:37 ` Hugh Dickins
2014-05-15 17:43 ` Sasha Levin
2014-05-15 17:58 ` Hugh Dickins
2013-04-10 8:02 ` Minchan Kim
2013-04-11 13:18 ` Kirill A. Shutemov
2013-04-14 7:13 ` Minchan Kim
2013-04-11 14:55 ` Sasha Levin
2013-04-11 15:13 ` Kirill A. Shutemov
2013-04-11 15:14 ` Sasha Levin
2013-04-24 22:46 ` Andrew Morton
2013-04-26 0:51 ` Sasha Levin
2013-04-26 2:01 ` Dave Jones
2013-04-26 3:12 ` Sasha Levin
2014-02-04 3:01 ` Sasha Levin
2014-02-04 3:59 ` Hugh Dickins
2014-02-04 16:58 ` Kirill A. Shutemov
2014-02-05 18:12 ` Sasha Levin
2014-02-05 22:50 ` Hugh Dickins
2013-04-24 22:51 ` H. Peter Anvin
2013-04-24 23:40 ` Simon Jeons [this message]
2013-04-26 2:28 ` H. Peter Anvin
2013-04-26 1:30 ` Minchan Kim
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=51786D52.1080509@gmail.com \
--to=simon.jeons@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.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;
as well as URLs for NNTP newsgroup(s).