From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH RFC v4 00/13] virtio-mem: paravirtualized memory Date: Fri, 13 Dec 2019 12:15:56 -0800 (PST) Message-ID: <20191213201556.GC26990@char.us.oracle.com> References: <20191212171137.13872-1-david@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20191212171137.13872-1-david@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: virtualization-bounces@lists.linux-foundation.org Sender: "Virtualization" To: David Hildenbrand Cc: Oscar Salvador , Michal Hocko , Robert Bradford , "Michael S . Tsirkin" , "Rafael J. Wysocki" , Pingfan Liu , Luiz Capitulino , linux-mm@kvack.org, Alexander Potapenko , Alexander Duyck , virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org, Mike Rapoport , Wei Yang , Anthony Yznaga , Dave Young , Len Brown , Pavel Tatashin , Pavel Tatashin , Anshuman Khandual , Qian Cai , Alexander Viro , Stefan Hajnoczi , Samuel Ortiz List-Id: virtualization@lists.linuxfoundation.org On Thu, Dec 12, 2019 at 06:11:24PM +0100, David Hildenbrand wrote: > This series is based on latest linux-next. The patches are located at: > https://github.com/davidhildenbrand/linux.git virtio-mem-rfc-v4 Heya! Would there be by any chance a virtio-spec git tree somewhere? ..snip.. > -------------------------------------------------------------------------- > 5. Future work > -------------------------------------------------------------------------- > > The separate patches contain a lot of future work items. One of the next > steps is to make memory unplug more likely to succeed - currently, there > are no guarantees on how much memory can get unplugged again. I have Or perhaps tell the caller why we can't and let them sort it out? For example: "Application XYZ is mlocked. Can't offload'.