From: David Hildenbrand Subject: Re: [PATCH v2 00/10] virtio-mem: paravirtualized memory Date: Tue, 14 Apr 2020 11:15:18 +0200 Message-ID: References: <20200311171422.10484-1-david@redhat.com> <20200329084128-mutt-send-email-mst@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: In-Reply-To: <20200329084128-mutt-send-email-mst@kernel.org> Content-Language: en-US To: "Michael S. Tsirkin" 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 , Sebastien Boeuf , Samuel Ortiz , Robert Bradford , Luiz Capitulino , Pankaj Gupta , teawater , Igor Mammedov , "Dr . David Alan Gilbert" , Alexander Duyck , Alexander Potapenko , Anshuman Khandual , Anthony Yznaga , Dan Williams , Dave Young , Jason Wang , Johannes Weiner List-Id: virtualization@lists.linuxfoundation.org On 29.03.20 14:42, Michael S. Tsirkin wrote: > On Wed, Mar 11, 2020 at 06:14:12PM +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-v2 >> >> I now have acks for all !virtio-mem changes. I'll be happy to get revi= ew >> feedback, testing reports, etc. for the virtio-mem changes. If there a= re >> no further comments, I guess this is good to go as a v1 soon. >=20 > I'd like to queue it for merge after the release. If you feel it's read= y > please ping me after the release to help make sure it didn't get > dropped. I see there were some reports about people having trouble > using this, pls keep working on this meanwhile. Hi Michael, I think this is ready to go as a first version. There are a couple of future work items related to kexec/kdump: - Teach kexec-tools/kexec_file_load() to not place the kexec kernel/initrd onto virtio-mem added memory. - Teach kexec-tools/kdump to consider a bigger number of memory resources for dumping. In general, as virtio-mem adds a lot of memory resources, we might want to tweak performance in that area as well. Future stuff. So I suggest queuing this. If you need a resend, please let me know. Cheers! --=20 Thanks, David / dhildenb