Re: [PATCH v4 00/30] KVM: x86: x86.{c,h} spring cleaning

[Sean Christopherson]

On Wed, Jun 24, 2026, Sean Christopherson wrote:
> On Wed, Jun 24, 2026, Paolo Bonzini wrote:
> > On 6/24/26 14:55, Sean Christopherson wrote:
> > > On Wed, Jun 24, 2026, Paolo Bonzini wrote:
> > > > On 6/13/26 02:02, Sean Christopherson wrote:
> > > > > It's still technically spring!
> > > > > 
> > > > > Perform spring cleaning on x86.{c,h} and asm/kvm_host.h, by adding regs.c
> > > > > (the kvm_cache_regs.h => regs.h is already applied) and msrs.{c,h}, and moving
> > > > > relevant code out of x86.c.
> > > > 
> > > > Rebased and applied to kvm/queue, with the following changes:
> > > > 
> > > > - Collect more tags
> > > > - Move enum kvm_apicv_inhibit to x86.h
> > > > - Move TSS constants to tss.h, include it in vmx.c
> > > > - Rename kvm_x86_vcpu_ioctl_get_sregs2 to kvm_vcpu_ioctl_x86_get_sregs2
> > > > - Rename kvm_x86_vcpu_ioctl_set_sregs2 to kvm_vcpu_ioctl_x86_set_sregs2
> > > > - Fix conflicts
> > > > - Changed srcu_dereference_check() to __force cast (see 18/30)
> > > > - Adjust commit message on patches 11 and 26
> > > 
> > > Shoot, I have a fully refreshed version that I was going to send today (well, I
> > > was going to send it on Monday, but life happened).  Any chance you want to wait
> > > and grab that?  It has all of the above (except for maybe rebasing?), along with
> > > a few more cleanups.
> > 
> > I was expecting some kind of conflict which is why I put it only on
> > kvm/queue.  If it's possible to have them on top, that would be helpful
> > because it means I can move what I have on kvm/next, before leaving for
> > vacation.
> 
> Roger that, I'll see how things look if I rebase on top asap, and report back.

Everything can go on top, and shouldn't generate massive conflicts, i.e. doesn't
need to be rushed into kvm/next and can go through kvm-x86.

Thanks much!