Re: [PATCH v1 00/11] virtio-mem: paravirtualized memory

2020-03-02 Thread David Hildenbrand
On 02.03.20 19:29, Michal Hocko wrote: > On Mon 02-03-20 19:15:09, David Hildenbrand wrote: > [...] >> As requested by Michal, I will squash some patches. > > Just to clarify. If I am the only one to care then do not bother. Oh, I do bother about your review comments a lot :) And pulling out the

Re: [PATCH v1 00/11] virtio-mem: paravirtualized memory

2020-03-02 Thread Michal Hocko
On Mon 02-03-20 19:15:09, David Hildenbrand wrote: [...] > As requested by Michal, I will squash some patches. Just to clarify. If I am the only one to care then do not bother. Btw. I still have patch 6 on the todo list to review. I just didn't find time for it today. -- Michal Hocko SUSE Labs _

Re: [PATCH v1 00/11] virtio-mem: paravirtualized memory

2020-03-02 Thread David Hildenbrand
On 02.03.20 14:49, David Hildenbrand wrote: > This series is based on latest linux-next. The patches are located at: > https://github.com/davidhildenbrand/linux.git virtio-mem-v1 > > The basic idea of virtio-mem is to provide a flexible, > cross-architecture memory hot(un)plug solution that av

[PATCH v1 00/11] virtio-mem: paravirtualized memory

2020-03-02 Thread David Hildenbrand
This series is based on latest linux-next. The patches are located at: https://github.com/davidhildenbrand/linux.git virtio-mem-v1 The basic idea of virtio-mem is to provide a flexible, cross-architecture memory hot(un)plug solution that avoids many limitations imposed by existing technologies