public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mhocko@kernel.org (Michal Hocko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] Revert "mm/page_alloc: fix memmap_init_zone pageblock alignment"
Date: Thu, 15 Mar 2018 19:21:10 +0100	[thread overview]
Message-ID: <20180315182110.GR23100@dhcp22.suse.cz> (raw)
In-Reply-To: <CAKv+Gu83VtB+ff6H88UMF9kiz5923U8tXhQoERdErYE4pQg94Q@mail.gmail.com>

On Thu 15-03-18 15:48:47, Ard Biesheuvel wrote:
> On 15 March 2018 at 15:34, Daniel Vacek <neelx@redhat.com> wrote:
[...]
> > Hence I was asking what is the abstract meaning
> > of it. As I see two *way_different* implementations so I am not sure
> > how I should understand that.
> >
> 
> My interpretation is that it has a struct page associated with it, but
> it seems the semantics of pfn_valid() aren't well defined.

Well, pfn_valid says that a given pfn is backed by a real memory and it
has a valid struct page backing it.
-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2018-03-15 18:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-14 19:29 [PATCH v2] Revert "mm/page_alloc: fix memmap_init_zone pageblock alignment" Ard Biesheuvel
2018-03-14 22:25 ` Jan Glauber
2018-03-14 22:53   ` Shanker Donthineni
2018-03-18 12:02     ` Neil Armstrong
2018-03-14 23:34 ` Linus Torvalds
2018-03-15  2:23 ` Daniel Vacek
2018-03-15  7:36   ` Ard Biesheuvel
2018-03-15  7:44     ` Daniel Vacek
2018-03-15  7:45       ` Ard Biesheuvel
2018-03-15 15:12         ` Daniel Vacek
2018-03-15 15:17           ` Ard Biesheuvel
2018-03-15 15:34             ` Daniel Vacek
2018-03-15 15:48               ` Ard Biesheuvel
2018-03-15 18:21                 ` Michal Hocko [this message]
2018-03-15 18:28                   ` Linus Torvalds
2018-03-15 18:35                     ` 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=20180315182110.GR23100@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --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