On 11/15/2017 02:19 PM, Hans van Kranenburg wrote:
> 
> [...]
> 
> I see that all the discussions linked above have gone silent quickly
> without a solution.

...because discussions continued in later versions of a patch...

> A post to the Xen mailing list on Aug 31th did not get any answer yet:
> https://lists.xen.org/archives/html/xen-users/2017-08/msg00092.html
> 
> I see that the issue got fixed by replacing the code with a new
> implementation of the same functionality. I guess this is a scenario
> that sometimes happens, not having a ready to go fix available for the
> previous LTS kernel.
> 
> So, what would be the best step forward here? Should we poke the Xen
> people a bit more to find out how to approach this, or get an opinion on
> the best and smallest patch to go with?

Latest work on this:

https://patchwork.kernel.org/patch/10035835/

"Applied to for-linus-4.15."

-- 
Hans van Kranenburg

Reply via email to