On 16 April 2018 at 10:19, Andrew Jones <drjo...@redhat.com> wrote: > This is the cleaner choice, but I wasn't opposed to the max-vcpus > query getting double-duty though. While the backporting argument is > a good point, I'm not sure we've ever really cared about what > issues backporters have had to endure when they cherry-pick features > before.
Well, mostly I didn't like the entangling of two different features, so we look for the presence of one by checking for the other. That's confusing going forward as well as awkward for backporting. Plus if we have a difficulty with detection of new kernel features like this we're probably going to run into it again in the future, so we might as well sort it out now... thanks -- PMM
