Re: [PATCH v19 for-4.14 00/13] VM forking

[Tamas K Lengyel <tamas@xxxxxxxxxxxxx>]

On Mon, Jun 1, 2020 at 11:11 AM George Dunlap <George.Dunlap@xxxxxxxxxx> wrote:
>
>
>
> > On Jun 1, 2020, at 4:07 PM, Paul Durrant <xadimgnik@xxxxxxxxx> wrote:
> >
> >> -----Original Message-----
> >> From: Xen-devel <xen-devel-bounces@xxxxxxxxxxxxxxxxxxxx> On Behalf Of 
> >> Tamas K Lengyel
> >> Sent: 01 June 2020 14:22
> >> To: xen-devel@xxxxxxxxxxxxxxxxxxxx
> >> Cc: Kevin Tian <kevin.tian@xxxxxxxxx>; Stefano Stabellini 
> >> <sstabellini@xxxxxxxxxx>; Tamas K Lengyel
> >> <tamas.lengyel@xxxxxxxxx>; Jun Nakajima <jun.nakajima@xxxxxxxxx>; Wei Liu 
> >> <wl@xxxxxxx>; Andrew Cooper
> >> <andrew.cooper3@xxxxxxxxxx>; Ian Jackson <ian.jackson@xxxxxxxxxxxxx>; 
> >> George Dunlap
> >> <george.dunlap@xxxxxxxxxx>; Tamas K Lengyel <tamas@xxxxxxxxxxxxx>; Jan 
> >> Beulich <jbeulich@xxxxxxxx>;
> >> Anthony PERARD <anthony.perard@xxxxxxxxxx>; Julien Grall <julien@xxxxxxx>; 
> >> Roger Pau Monné
> >> <roger.pau@xxxxxxxxxx>
> >> Subject: [PATCH v19 for-4.14 00/13] VM forking
> >
> > Hi,
> >
> >  This series looks to be largely un-acked so, since we are now past the 
> > freeze date, I don't really think it can go into 4.14. Is there a 
> > particular reason that you think it should be considered?
>
> Tamas’ project itself mainly uses libxc and below, as I understand; and so 
> getting patches 1 and 2 in would be an important milestone; both have had 
> R-b’s before the feature freeze.  Arguably patches 1 and 2 are a bug fix.  
> Patch 1 is missing VMX (or a general x86).

Correct. The first two patches going in would decide whether we will
be able to use the 4.14 release without having to carry out-of-tree
patches. Although as things stand at the moment regarding all the bugs
being discovered in 4.13 and 4.14 we will likely still have to
backport all of these patches to 4.12 by hand.

> The libxl/xl side hasn’t, as I understand it, had significant review; I think 
> that should probably wait until 4.15.

Correct. It has been sent 19 times so far over a period of 9 months
with no feedback from any of the maintainers other then that it's hard
to review. We had some good discussion with other community members
but evidently non of the toolstack maintainers care too much about it.
I made the last-ditch effort to make it easier to review but at this
point we started implementing our own toolstack to interact with VM
forks.

> What do you think, Tamas?

If it's not going into 4.14 then it's going to be dropped. It has been
made solely for the benefit of the community to make the new VM
forking more accessible and useful for others. Without it the only way
to use the feature is to implement your own toolstack. Initially we
were hoping that integrating support to xl/libxl would eliminate the
need for us to implement our own parallel toolstack but since we have
to do that now anyway there is no benefit for us in carrying these
patches any further. It's disheartening we had to resort to that and I
certainly will try to avoid contributing to xl/libxl in the future
since I personally consider it a waste of time.

Thanks,
Tamas