On Tue, Apr 14, 2020 at 11:15:18AM +0200, David Hildenbrand wrote: > 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 review > >> feedback, testing reports, etc. for the virtio-mem changes. If there are > >> no further comments, I guess this is good to go as a v1 soon. > > > > I'd like to queue it for merge after the release. If you feel it's ready > > 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! Thanks! I'll queue it for merge after the release. If possible please ping me after the release to help make sure it didn't get dropped. > -- > Thanks, > > David / dhildenb
