All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reza Arbab <arbab@linux.vnet.ibm.com>
To: Alistair Popple <apopple@au1.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Stewart Smith <stewart@linux.vnet.ibm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tang Chen <tangchen@cn.fujitsu.com>,
	linux-mm@kvack.org,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Bharata B Rao <bharata@linux.vnet.ibm.com>,
	Nathan Fontenot <nfont@linux.vnet.ibm.com>
Subject: Re: [PATCH v4 2/5] drivers/of: do not add memory for unavailable nodes
Date: Sat, 22 Oct 2016 20:51:08 -0500	[thread overview]
Message-ID: <20161023015107.527l4fvnh2nrup5u@arbab-vm> (raw)
In-Reply-To: <2344394.NlaWgtFOqB@new-mexico>

Hi Alistair,

On Fri, Oct 21, 2016 at 05:22:54PM +1100, Alistair Popple wrote:
>From what I can tell it seems that kernels without this patch will try 
>and use this memory even if it is marked in the device-tree as 
>status="disabled" which could lead to problems for older kernels when 
>we start exporting this property from firmware.
>
>Arguably this might not be such a problem in practice as we probably 
>don't have many (if any) existing kernels that will boot on hardware 
>exporting these properties.

Yes, I think you've got it right.

>However given this patch seems fairly independent perhaps it is worth 
>sending as a separate fix if it is not going to make it into this 
>release?

Michael,

If this set as a whole is going to miss the release, would it be helpful 
for me to resend 1/5 and 2/5 as a separate set? They are the minimum 
needed to prevent the possible forward compatibility issue Alistair 
describes.

-- 
Reza Arbab

WARNING: multiple messages have this Message-ID (diff)
From: Reza Arbab <arbab@linux.vnet.ibm.com>
To: Alistair Popple <apopple@au1.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Stewart Smith <stewart@linux.vnet.ibm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tang Chen <tangchen@cn.fujitsu.com>,
	linux-mm@kvack.org,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Bharata B Rao <bharata@linux.vnet.ibm.com>,
	Nathan Fontenot <nfont@linux.vnet.ibm.com>
Subject: Re: [PATCH v4 2/5] drivers/of: do not add memory for unavailable nodes
Date: Sat, 22 Oct 2016 20:51:08 -0500	[thread overview]
Message-ID: <20161023015107.527l4fvnh2nrup5u@arbab-vm> (raw)
In-Reply-To: <2344394.NlaWgtFOqB@new-mexico>

Hi Alistair,

On Fri, Oct 21, 2016 at 05:22:54PM +1100, Alistair Popple wrote:
>From what I can tell it seems that kernels without this patch will try 
>and use this memory even if it is marked in the device-tree as 
>status="disabled" which could lead to problems for older kernels when 
>we start exporting this property from firmware.
>
>Arguably this might not be such a problem in practice as we probably 
>don't have many (if any) existing kernels that will boot on hardware 
>exporting these properties.

Yes, I think you've got it right.

>However given this patch seems fairly independent perhaps it is worth 
>sending as a separate fix if it is not going to make it into this 
>release?

Michael,

If this set as a whole is going to miss the release, would it be helpful 
for me to resend 1/5 and 2/5 as a separate set? They are the minimum 
needed to prevent the possible forward compatibility issue Alistair 
describes.

-- 
Reza Arbab

--
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>

  reply	other threads:[~2016-10-23  1:51 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06 18:36 [PATCH v4 0/5] powerpc/mm: movable hotplug memory nodes Reza Arbab
2016-10-06 18:36 ` Reza Arbab
2016-10-06 18:36 ` [PATCH v4 1/5] drivers/of: introduce of_fdt_device_is_available() Reza Arbab
2016-10-06 18:36   ` Reza Arbab
2016-10-06 18:36 ` [PATCH v4 2/5] drivers/of: do not add memory for unavailable nodes Reza Arbab
2016-10-06 18:36   ` Reza Arbab
2016-10-11 13:58   ` Rob Herring
2016-10-11 13:58     ` Rob Herring
2016-10-21  6:22   ` Alistair Popple
2016-10-21  6:22     ` Alistair Popple
2016-10-23  1:51     ` Reza Arbab [this message]
2016-10-23  1:51       ` Reza Arbab
2016-10-24 10:24     ` Michael Ellerman
2016-10-24 10:24       ` Michael Ellerman
2016-10-24 18:20       ` Reza Arbab
2016-10-24 18:20         ` Reza Arbab
2016-10-24 18:20         ` Reza Arbab
2016-10-06 18:36 ` [PATCH v4 3/5] powerpc/mm: allow memory hotplug into a memoryless node Reza Arbab
2016-10-06 18:36   ` Reza Arbab
2016-10-20  3:30   ` Balbir Singh
2016-10-20  3:30     ` Balbir Singh
2016-10-20  3:30     ` Balbir Singh
2016-10-20 14:38     ` Reza Arbab
2016-10-20 14:38       ` Reza Arbab
2016-10-20 14:38       ` Reza Arbab
2016-10-25  9:39     ` Michael Ellerman
2016-10-25  9:39       ` Michael Ellerman
2016-10-06 18:36 ` [PATCH v4 4/5] mm: make processing of movable_node arch-specific Reza Arbab
2016-10-06 18:36   ` Reza Arbab
2016-10-06 18:36   ` Reza Arbab
2016-10-07  6:37   ` Aneesh Kumar K.V
2016-10-07  6:37     ` Aneesh Kumar K.V
2016-10-07  6:37     ` Aneesh Kumar K.V
2016-10-11 12:26   ` Balbir Singh
2016-10-11 12:26     ` Balbir Singh
2016-10-25 12:15     ` Balbir Singh
2016-10-25 12:15       ` Balbir Singh
2016-10-25 15:55       ` Reza Arbab
2016-10-25 15:55         ` Reza Arbab
2016-10-25 22:34         ` Balbir Singh
2016-10-25 22:34           ` Balbir Singh
2016-10-26  0:49           ` Reza Arbab
2016-10-26  0:49             ` Reza Arbab
2016-10-26 10:52             ` Michael Ellerman
2016-10-26 10:52               ` Michael Ellerman
2016-10-26 17:03               ` Reza Arbab
2016-10-26 17:03                 ` Reza Arbab
2016-10-25 22:59         ` Balbir Singh
2016-10-25 22:59           ` Balbir Singh
2016-10-06 18:36 ` [PATCH v4 5/5] mm: enable CONFIG_MOVABLE_NODE on non-x86 arches Reza Arbab
2016-10-06 18:36   ` Reza Arbab
2016-10-07  6:40   ` Aneesh Kumar K.V
2016-10-07  6:40     ` Aneesh Kumar K.V
2016-10-11 13:17   ` Balbir Singh
2016-10-11 13:17     ` Balbir Singh

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=20161023015107.527l4fvnh2nrup5u@arbab-vm \
    --to=arbab@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=apopple@au1.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=robh+dt@kernel.org \
    --cc=stewart@linux.vnet.ibm.com \
    --cc=tangchen@cn.fujitsu.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.