On 03/02/21 18:54, Sean Christopherson wrote:
On Wed, Feb 03, 2021, Paolo Bonzini wrote:
Looks good! I'll wait for a few days of reviews,
I guess I know what I'm doing this afternoon :-)
but I'd like to queue this for 5.12 and I plan to make it the default in 5.13
or 5.12-rc (depending on when I can ask Red Hat QE to give it a shake).
Hmm, given that kvm/queue doesn't seem to get widespread testing, I think it
should be enabled by default in rc1 for whatever kernel it targets.
Would it be too heinous to enable it by default in 5.12-rc1, knowing full well
that there's a good possibility it would get reverted?
Absolutely not. However, to clarify my plan:
- what is now kvm/queue and has been reviewed will graduate to kvm/next
in a couple of days, and then to 5.12-rc1. Ben's patches are already in
kvm/queue, but there's no problem in waiting another week before moving
them to kvm/next because it's not enabled by default. (Right now even
CET is in kvm/queue, but it will not move to kvm/next until bare metal
support is in).
- if this will not have been tested by Red Hat QE by say 5.12-rc3, I
would enable it in kvm/next instead, and at that point the target would
become the 5.13 merge window (and release).
Paolo
