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=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 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 C8C6ACA9EA0 for ; Tue, 22 Oct 2019 08:21:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9ECFB20684 for ; Tue, 22 Oct 2019 08:21:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1571732494; bh=svEmo0VcGl30wqPCYYcPveU6XSA9nqCJthRA3sn3PVM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=CuEG4f8u7v8NzdyrxPPx9wmLoskycQH8qqML1hyhnAF6rctz9368LkCB/RsutX8Q1 TD9bMgpxojIzJng52FhAhS/WHNB6jGnHZA5Vmx2BwB5wfv7O/aJaBT616h5a2xSsHc db5jJAPcVhlclu3qv9HRyVRPDx8Vy8WJqilzxueM= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388360AbfJVIVd (ORCPT ); Tue, 22 Oct 2019 04:21:33 -0400 Received: from mx2.suse.de ([195.135.220.15]:36794 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2388011AbfJVIVd (ORCPT ); Tue, 22 Oct 2019 04:21:33 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id BBD6CB150; Tue, 22 Oct 2019 08:21:31 +0000 (UTC) Date: Tue, 22 Oct 2019 10:21:31 +0200 From: Michal Hocko To: David Hildenbrand Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Alexander Duyck , Andrew Morton , Anshuman Khandual , Dan Williams , Mel Gorman , Mike Rapoport , Mike Rapoport , Oscar Salvador , Pavel Tatashin , Pavel Tatashin , Pingfan Liu , Qian Cai , Vlastimil Babka , Wei Yang Subject: Re: [PATCH v2 0/2] mm: Memory offlining + page isolation cleanups Message-ID: <20191022082131.GC9379@dhcp22.suse.cz> References: <20191021172353.3056-1-david@redhat.com> <25d3f071-3268-298b-e0c8-9c307d1015fe@redhat.com> <20191022080835.GZ9379@dhcp22.suse.cz> <1f56744d-2c22-6c12-8fe8-4a71e791c467@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1f56744d-2c22-6c12-8fe8-4a71e791c467@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 22-10-19 10:15:07, David Hildenbrand wrote: > On 22.10.19 10:08, Michal Hocko wrote: > > On Tue 22-10-19 08:52:28, David Hildenbrand wrote: > > > On 21.10.19 19:23, David Hildenbrand wrote: > > > > Two cleanups that popped up while working on (and discussing) virtio-mem: > > > > https://lkml.org/lkml/2019/9/19/463 > > > > > > > > Tested with DIMMs on x86. > > > > > > > > As discussed with michal in v1, I'll soon look into removing the use > > > > of PG_reserved during memory onlining completely - most probably > > > > disallowing to offline memory blocks with holes, cleaning up the > > > > onlining+offlining code. > > > > > > BTW, I remember that ZONE_DEVICE pages are still required to be set > > > PG_reserved. That has to be sorted out first. > > > > Do they? > > Yes, especially KVM code :/ Details please? -- Michal Hocko SUSE Labs