On Thu, Nov 19, 2015 at 10:39:05AM +0800, Xiao Guangrong wrote: > > > On 11/19/2015 04:44 AM, Michael S. Tsirkin wrote: > >On Wed, Nov 18, 2015 at 05:18:17PM -0200, Eduardo Habkost wrote: > >>On Wed, Nov 18, 2015 at 09:59:34AM +0800, Xiao Guangrong wrote: > >>> > >>>Ping... > >>> > >>>Do you have any comment on this patchset? Could it be applied to somewhere > >>>if it is okay for you? > >> > >>I have no additional comments, as the memory-backend patches I > >>was reviewing are not included in this version. I didn't take the > >>time to review the TYPE_NVDIMM and ACPI changes. > > > >No, I don't think the way guest memory is allocated here is ok. I'm > > Since the DSM memory/ACPI memory was not included in this patchset, i really > do not understand what is "guest memory is allocated" exactly stands for... I might even be confusing this with another patchset. Let's have this discussion when I have the time to review and respond properly. > >sorry, I'm busy with 2.5 now, and this is clearly not 2.5 material. > > I still see some pull requests were send our for 2.5 merge window today and > yesterday ... > > This patchset is the simplest version we can figure out to implement basic > functionality for vNVDIMM and only minor change is needed for other code. > It would be nice and really appreciate if it can go to 2.5. Sorry, no way, we are in a bugfix only mode for 2.5. > >Once that's out, I'll post some suggestions. > > Look forward to you suggestions. > > Thanks for your time, Michael and Eduardo! -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
