All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Patch "KVM: VMX: Convert vcpu_vmx.exit_reason to a union" has been added to the 5.10-stable tree
Date: Tue, 20 Apr 2021 16:56:06 +0000	[thread overview]
Message-ID: <YH8Hph/VEotO+Iv+@google.com> (raw)
In-Reply-To: <YH4HlIEvoqHWFtz+@sashalap>

On Mon, Apr 19, 2021, Sasha Levin wrote:
> On Mon, Apr 19, 2021 at 09:54:18PM +0000, Sean Christopherson wrote:
> > Maybe we'll end up with a more painful conflict in the future that would be best
> > solved by grabbing this refactoring, but I don't think we're there yet.
> 
> This is the tricky part: when we start having these conflicts it's
> usually too late to refactor, no one cares, and backports just don't
> happen.
> 
> I'd actually point to the file shuffling (commits like a821bab2d1ee
> ("KVM: VMX: Move VMX specific files to a "vmx" subdirectory")) you did a
> few years ago in arch/x86/kvm/ as an example to why we can't wait: those
> changes made a lot of sense upstream, but for stable kernels it meant
> that patches were now trying to touch the wrong files and would often
> fail or do the wrong thing.
> 
> On hindsight, we probably should have moved files around in stable trees
> as well to match what upstream had, but at this point it's too late to
> go back and fix that, and we're stuck manually editing paths for the
> lifetime of most of the LTS trees.

And I guess there's also the argument that inducing even a handful of manual
backports is more risky overall than taking this one "unnecessary" patch.

Objection withdrawn, I don't have a strong opinion either way :-)

      reply	other threads:[~2021-04-20 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210419002733.D5675610CB@mail.kernel.org>
2021-04-19 21:54 ` Patch "KVM: VMX: Convert vcpu_vmx.exit_reason to a union" has been added to the 5.10-stable tree Sean Christopherson
2021-04-19 22:43   ` Sasha Levin
2021-04-20 16:56     ` Sean Christopherson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YH8Hph/VEotO+Iv+@google.com \
    --to=seanjc@google.com \
    --cc=pbonzini@redhat.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.