Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936985AbcKNTfE (ORCPT ); Mon, 14 Nov 2016 14:35:04 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:50047 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S936479AbcKNTfB (ORCPT ); Mon, 14 Nov 2016 14:35:01 -0500 Date: Mon, 14 Nov 2016 13:34:52 -0600 From: Reza Arbab To: Michael Ellerman Cc: Benjamin Herrenschmidt , Paul Mackerras , Andrew Morton , Rob Herring , Frank Rowand , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org, devicetree@vger.kernel.org, Bharata B Rao , Nathan Fontenot , Stewart Smith , Alistair Popple , Balbir Singh , "Aneesh Kumar K.V" , linux-kernel@vger.kernel.org Subject: Re: [PATCH v6 4/4] of/fdt: mark hotpluggable memory References: <1478562276-25539-1-git-send-email-arbab@linux.vnet.ibm.com> <1478562276-25539-5-git-send-email-arbab@linux.vnet.ibm.com> <87bmxii85s.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <87bmxii85s.fsf@concordia.ellerman.id.au> Organization: IBM Linux Technology Center User-Agent: NeoMutt/20161104 (1.7.1) X-TM-AS-GCONF: 00 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16111419-0024-0000-0000-000015061571 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00006077; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000189; SDB=6.00780655; UDB=6.00376467; IPR=6.00558156; BA=6.00004878; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00013324; XFM=3.00000011; UTC=2016-11-14 19:34:58 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 16111419-0025-0000-0000-00004622B50D Message-Id: <20161114193451.bzowsi6csesoxwap@arbab-laptop.austin.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-11-14_12:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609300000 definitions=main-1611140384 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 652 Lines: 20 On Mon, Nov 14, 2016 at 10:59:43PM +1100, Michael Ellerman wrote: >So I'm not opposed to this, but it is a little vague. > >What does the "hotpluggable" property really mean? > >Is it just a hint to the operating system? (which may or may not be >Linux). > >Or is it a direction, "this memory must be able to be hotunplugged"? > >I think you're intending the former, ie. a hint, which is probably OK. >But it needs to be documented clearly. Yes, you've got it right. It's just a hint, not a mandate. I'm about to send v7 which adds a description of "hotpluggable" in the documentation. Hopefully I've explained it well enough there. -- Reza Arbab