Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4577428ybb; Tue, 14 Apr 2020 09:58:21 -0700 (PDT) X-Google-Smtp-Source: APiQypKotFHShWbWZrbQu2XpFU3DlIyenWgHS+oxuau+D7LlrBYpm9moaqVHOSFQSvOO+61WHLfD X-Received: by 2002:a17:906:3047:: with SMTP id d7mr1059608ejd.141.1586883501001; Tue, 14 Apr 2020 09:58:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586883500; cv=none; d=google.com; s=arc-20160816; b=eHvZt8nhzvTH0yNMErTdyyZRI/t9qPeHLPEUv3D87HLrr5RPzH9hiZme6a1oeXJkA8 XuInt0FUbVWLd14BMVBbJI/qViMLHKOdpIVHojURbLSmzEfCkvfRBK8EKQJuOBqRH/X3 8WuvLWpGraBT2RE10kYUiZhAbfKq1Mnu68MTyIcR+CEkPHh09wf+OKPz+xRQ0hbAuI3S ma7cXbVSS0webzIWK/2z033AH7lN74guLhf/7vEXjdVkQUU5CD7SUohL/sNu33lXmw9U zYUDHkbyA/9LxXLcedzAMnYOKSnkDDZpX2fGxVdVDQ8Vrm3ziI76Y/St/a5Qihb8PLPD qTLg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=a+z0V7RnGWnuMpMvNgwDiJGASaPb4ctVzlcABrxuV4A=; b=w+zz9Orgk0T9ZP4VuF+z1UCiCdk5nRx9Y5rL7ssmKwwoHp9oGQaJvosg0NbaSYGb6A x8YTQi0yqu7KR9C2tZbRR9xapvO63Hph22Q1tSZXXlmIN5ql2sENC0KwcDrKsiSRH0NA RrAUhwtCW5mIKhP7qB0TmzmaFDlKJ4rQ0sctAf9k4uWbzvGWuOBqfH0kk+5pp3SPEXj+ tPGr9WUo3JYQc5sh/nkI/SGKp8JNs+BwC1IlLviCtHvheN40cdZZ2aOaCwJR/JjGqZR6 BG55/3zfe6sPqlzvFObY6objaUKxNKdw9WaETOfD3D8GnjZmdkCDG+yyNuV617KPPGDL I5jw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=IYW8ewKU; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dt23si8783903ejb.349.2020.04.14.09.57.56; Tue, 14 Apr 2020 09:58:20 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=IYW8ewKU; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391792AbgDNQf2 (ORCPT + 99 others); Tue, 14 Apr 2020 12:35:28 -0400 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:24912 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391769AbgDNQfP (ORCPT ); Tue, 14 Apr 2020 12:35:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1586882113; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=a+z0V7RnGWnuMpMvNgwDiJGASaPb4ctVzlcABrxuV4A=; b=IYW8ewKU4uhcM8rcB4EdFu7tsMh9y+ergjepQJIMULG0WSCujseGGzHnGtj+gHVbRGpf81 0mqIWU3rka5PJr3fX8SNaS8hIJK6U7XfoGlN9ohyT/YkIP5IajncroCMenX4XEbTFKnDvi YVHEjx0iCw4jPy+PViePvUpQM8vvc88= Received: from mail-qt1-f200.google.com (mail-qt1-f200.google.com [209.85.160.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-8-gd56TpfyPM2tKsTIuBK-Cg-1; Tue, 14 Apr 2020 12:35:08 -0400 X-MC-Unique: gd56TpfyPM2tKsTIuBK-Cg-1 Received: by mail-qt1-f200.google.com with SMTP id g14so10420470qts.7 for ; Tue, 14 Apr 2020 09:35:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=a+z0V7RnGWnuMpMvNgwDiJGASaPb4ctVzlcABrxuV4A=; b=cx4vPI32ClS4OZQE+Mc+rpMhgV+doFhR7y+98Y+hAXpCVUQP4tbE/CmSS8coAR7y+a FFS7qpryxu6uO0CC0imaeto2w8KuiP2tN5IxClXCqXNpIx3DgQlb8nKZkp18xKyGI/3T kr8ctRbII5j5WG1ZffFjveiI/9CBpgWtco4B/iYm7FF+GmXmKOUa/G/1XkVeFVBaXlpy VpU2FIyF7iNnb5a1KeBrRRiygveBn/ilUSbzEpm6C/aHSBdNET9YRc+DGzveC7v9oADm T73NwBbI3dQLeZrg3ZJt4CL8zl5QWWBMS60JoY4nV6AU6fFnDR/0ifxYHGWfta53bp4E 7BoQ== X-Gm-Message-State: AGi0Pua3B8kAO6jtJGZZeDO5zQIr0K2yeDFhq90C60e3w3MQmCmkmuea JGBh+m289E+KH0HROsxuWVfIOAszJn2r4Fyf7uxR0pfJQj/rQyU3avH3B/8kpXRjrTVfxcvrXJF DqNWud0Lx5tPigAvS4fBkfWL3 X-Received: by 2002:ac8:1a8a:: with SMTP id x10mr16745178qtj.154.1586882108242; Tue, 14 Apr 2020 09:35:08 -0700 (PDT) X-Received: by 2002:ac8:1a8a:: with SMTP id x10mr16745153qtj.154.1586882108008; Tue, 14 Apr 2020 09:35:08 -0700 (PDT) Received: from redhat.com (bzq-79-183-51-3.red.bezeqint.net. [79.183.51.3]) by smtp.gmail.com with ESMTPSA id f1sm10297177qkl.91.2020.04.14.09.35.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Apr 2020 09:35:07 -0700 (PDT) Date: Tue, 14 Apr 2020 12:35:02 -0400 From: "Michael S. Tsirkin" To: David Hildenbrand Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, virtio-dev@lists.oasis-open.org, virtualization@lists.linux-foundation.org, kvm@vger.kernel.org, Michal Hocko , Andrew Morton , Oscar Salvador , Michal Hocko , Pavel Tatashin , Wei Yang , Dan Williams , Qian Cai Subject: Re: [PATCH v2 07/10] mm/memory_hotplug: Introduce offline_and_remove_memory() Message-ID: <20200414123438-mutt-send-email-mst@kernel.org> References: <20200311171422.10484-1-david@redhat.com> <20200311171422.10484-8-david@redhat.com> <156601a9-e919-b88f-2278-97ecee554d21@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <156601a9-e919-b88f-2278-97ecee554d21@redhat.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 11, 2020 at 06:19:04PM +0100, David Hildenbrand wrote: > On 11.03.20 18:14, David Hildenbrand wrote: > > virtio-mem wants to offline and remove a memory block once it unplugged > > all subblocks (e.g., using alloc_contig_range()). Let's provide > > an interface to do that from a driver. virtio-mem already supports to > > offline partially unplugged memory blocks. Offlining a fully unplugged > > memory block will not require to migrate any pages. All unplugged > > subblocks are PageOffline() and have a reference count of 0 - so > > offlining code will simply skip them. > > > > All we need is an interface to offline and remove the memory from kernel > > module context, where we don't have access to the memory block devices > > (esp. find_memory_block() and device_offline()) and the device hotplug > > lock. > > > > To keep things simple, allow to only work on a single memory block. > > > > Lost the ACK from Michael > > Acked-by: Michal Hocko [1] > > [1] https://lkml.kernel.org/r/20200302142737.GP4380@dhcp22.suse.cz Andrew, could you pls ack merging this through the vhost tree, with the rest of the patchset? > -- > Thanks, > > David / dhildenb