Re: [PATCH v2 00/10] virtio-mem: paravirtualized memory

From: David Hildenbrand <david@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
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 <mhocko@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Sebastien Boeuf <sebastien.boeuf@intel.com>,
	Samuel Ortiz <samuel.ortiz@intel.com>,
	Robert Bradford <robert.bradford@intel.com>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
	teawater <teawaterz@linux.alibaba.com>,
	Igor Mammedov <imammedo@redhat.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	Alexander Potapenko <glider@google.com>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Anthony Yznaga <anthony.yznaga@oracle.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Dave Young <dyoung@redhat.com>, Jason Wang <jasowang@redhat.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Juergen Gross <jgross@suse.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Len Brown <lenb@kernel.org>,
	Mel Gorman <mgorman@techsingularity.net>,
	Michal Hocko <mhocko@suse.com>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Oscar Salvador <osalvador@suse.com>,
	Oscar Salvador <osalvador@suse.de>,
	Pavel Tatashin <pasha.tatashin@soleen.com>,
	Pavel Tatashin <pavel.tatashin@microsoft.com>,
	Pingfan Liu <kernelfans@gmail.com>, Qian Cai <cai@lca.pw>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Wei Yang <richard.weiyang@gmail.com>
Subject: Re: [PATCH v2 00/10] virtio-mem: paravirtualized memory
Date: Tue, 14 Apr 2020 20:39:25 +0200	[thread overview]
Message-ID: <758aa88e-7bd1-ea77-6ee3-9a015a0f8b0e@redhat.com> (raw)
In-Reply-To: <20200414122716-mutt-send-email-mst@kernel.org>

On 14.04.20 18:28, Michael S. Tsirkin wrote:
> 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.

If we could get this into 5.8, that would be great (IOW, have it in
-next for a while before the 5.8 merge window opens).

Thanks!

-- 
Thanks,

David / dhildenb