From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D0588C352BE for ; Fri, 17 Apr 2020 15:02:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AB98E2223C for ; Fri, 17 Apr 2020 15:02:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="OotAlMJE" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728459AbgDQPCN (ORCPT ); Fri, 17 Apr 2020 11:02:13 -0400 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:58205 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728381AbgDQPCI (ORCPT ); Fri, 17 Apr 2020 11:02:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1587135727; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=zAUQ1fejVgK8xdiFLC8Kzo6yupRq84Rn11njknDDfkc=; b=OotAlMJETxPt9KIPFVhd4AOsVRSMq29/PVkTkjyC9xHqo43R9l6+W63RCa5kStqCTG4PM1 0kGBYbS0537F4w11OHPWa/ZCppSpL5R9l8tW8kftGdYZC8ScBHT3JYAkzvvdPoQMOxapGZ xOSitaEARzZQ7drDjNrDbruxLhL3hfo= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-86-qKoBkKQ3NGO4Eh09TUhtLQ-1; Fri, 17 Apr 2020 11:01:59 -0400 X-MC-Unique: qKoBkKQ3NGO4Eh09TUhtLQ-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A34BE800D5C; Fri, 17 Apr 2020 15:01:57 +0000 (UTC) Received: from t480s.redhat.com (ovpn-114-107.ams2.redhat.com [10.36.114.107]) by smtp.corp.redhat.com (Postfix) with ESMTP id BC3C8A09B9; Fri, 17 Apr 2020 15:01:52 +0000 (UTC) From: David Hildenbrand To: linux-kernel@vger.kernel.org Cc: linux-mm@kvack.org, linux-s390@vger.kernel.org, David Hildenbrand , Christian Borntraeger , Heiko Carstens , Kirill Smelkov , Michael Holzheu , Philipp Rudo , Vasily Gorbik Subject: [PATCH RFC 0/2] s390/mm: don't set ARCH_KEEP_MEMBLOCK Date: Fri, 17 Apr 2020 17:01:49 +0200 Message-Id: <20200417150151.17239-1-david@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Looking into why we still create memblocks for hotplugged memory (via add_memory()), I discovered that we might not need ARCH_KEEP_MEMBLOCK on s390x after all. After [1] we will no longer create memblocks for hotplugged memory in case of !CONFIG_ARCH_KEEP_MEMBLOCK. With this series, the same will apply to standby memory on s390x, added via add_memory(). [1] https://lkml.kernel.org/r/20200416104707.20219-1-david@redhat.com David Hildenbrand (2): s390/zcore: traverse resources instead of memblocks s390/mm: don't set ARCH_KEEP_MEMBLOCK arch/s390/Kconfig | 1 - drivers/s390/char/zcore.c | 61 ++++++++++++++++++++++++++++++--------- 2 files changed, 48 insertions(+), 14 deletions(-) --=20 2.25.1