Hi! On 8/17/26 18:52, Jared Rossi wrote:
I see what you mean. I think an argument can be made for any case, but I’m not sure what is most desirable for QEMU stable. I’ll try to clarify the problem.
Yeah, this is what I mean, maybe not as clear as in your explanation.
So, as I see it, there are three possible approaches: 1) Do nothing for now, which means the maximum loadparm value is effectively 30 instead of 31 until both a4adf071dc7 and the proposed fix are applied together later, but it is otherwise fine
This is what I'm going to do - nothing. In 10.0.x this is not a problem, and the other feature changes (like letting to specify the value using loadparm) should not be picked up there. And this is basically what my previous email stated - I'm applying it to 11.0 & 11.1, but not to 10.0 :) Thank you for the explanations! /mjt
