The first change completes a several years old but still incomplete
change. As mentioned there, reverting the original change may also
be an option. The second change works around some odd libxl behavior,
as described in [1]. As per a response to that mail addressing the
issue in libxl may also be possible, but it's not clear to me who
would get to doing so at which point in time. Hence the kernel side
alternative is being proposed here.

As to Konrad being on the Cc list: I find it puzzling that he's
listed under "XEN PCI SUBSYSTEM", but pciback isn't considered part
of this.

1: redo VF placement in the virtual topology
2: reconfigure also from backend watch handler

Jan

[1] https://lists.xen.org/archives/html/xen-devel/2021-03/msg00956.html

On 18.05.21 18:12, Jan Beulich wrote:
> The first change completes a several years old but still incomplete
> change. As mentioned there, reverting the original change may also
> be an option. The second change works around some odd libxl behavior,
> as described in [1]. As per a response to that mail addressing the
> issue in libxl may also be possible, but it's not clear to me who
> would get to doing so at which point in time. Hence the kernel side
> alternative is being proposed here.
> 
> As to Konrad being on the Cc list: I find it puzzling that he's
> listed under "XEN PCI SUBSYSTEM", but pciback isn't considered part
> of this.
> 
> 1: redo VF placement in the virtual topology
> 2: reconfigure also from backend watch handler

Series pushed to xen/tip.git for-linus-5.13b


Juergen