Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753538AbdLDMo3 (ORCPT ); Mon, 4 Dec 2017 07:44:29 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:44872 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752166AbdLDMo2 (ORCPT ); Mon, 4 Dec 2017 07:44:28 -0500 Date: Mon, 4 Dec 2017 12:44:19 +0000 From: Andrea Reale To: Michal Hocko Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, m.bielski@virtualopensystems.com, arunks@qti.qualcomm.com, mark.rutland@arm.com, scott.branden@broadcom.com, will.deacon@arm.com, qiuxishi@huawei.com, catalin.marinas@arm.com, realean2@ie.ibm.com Subject: Re: [PATCH v2 4/5] mm: memory_hotplug: Add memory hotremove probe device References: <22d34fe30df0fbacbfceeb47e20cb1184af73585.1511433386.git.ar@linux.vnet.ibm.com> <20171130144905.ntpovhy66gekj6e6@dhcp22.suse.cz> <20171204115129.GD6373@samekh> <20171204123355.4tam7pfv34zmwzyu@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20171204123355.4tam7pfv34zmwzyu@dhcp22.suse.cz> User-Agent: Mutt/1.5.24 (2015-08-30) X-TM-AS-GCONF: 00 x-cbid: 17120412-0016-0000-0000-0000050924FB X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17120412-0017-0000-0000-000028451B5E Message-Id: <20171204124419.GB10599@samekh> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-12-04_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1712040185 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1358 Lines: 44 On Mon 4 Dec 2017, 13:33, Michal Hocko wrote: > On Mon 04-12-17 11:51:29, Andrea Reale wrote: > > On Thu 30 Nov 2017, 15:49, Michal Hocko wrote: > > > On Thu 23-11-17 11:14:52, Andrea Reale wrote: > > > > Adding a "remove" sysfs handle that can be used to trigger > > > > memory hotremove manually, exactly simmetrically with > > > > what happens with the "probe" device for hot-add. > > > > > > > > This is usueful for architecture that do not rely on > > > > ACPI for memory hot-remove. > > > > > > As already said elsewhere, this really has to check the online status of > > > the range and fail some is still online. > > > > > > > This is actually still done in remove_memory() (patch 2/5) with > > walk_memory_range. We just return an error rather than BUGing(). > > > > Or are you referring to something else? > > But you are not returning that error to the caller, are you? > > [...] Oh, I see your point. Yes, indeed we should have returned it. Thanks for catching the issue. > > > > + nid = memory_add_physaddr_to_nid(phys_addr); > > > > + ret = lock_device_hotplug_sysfs(); > > > > + if (ret) > > > > + return ret; > > > > + > > > > + remove_memory(nid, phys_addr, > > > > + MIN_MEMORY_BLOCK_SIZE * sections_per_block); > > > > + unlock_device_hotplug(); > > > > + return count; Thanks, Andrea > > -- > Michal Hocko > SUSE Labs >