[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZyUCSZEv4w1yXwEb@google.com>
Date: Fri, 1 Nov 2024 09:31:05 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Oliver Upton <oliver.upton@...ux.dev>
Cc: Mark Brown <broonie@...nel.org>, Marc Zyngier <maz@...nel.org>, Anup Patel <anup@...infault.org>,
Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Paolo Bonzini <pbonzini@...hat.com>,
Christian Borntraeger <borntraeger@...ux.ibm.com>, Janosch Frank <frankja@...ux.ibm.com>,
Claudio Imbrenda <imbrenda@...ux.ibm.com>, linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.linux.dev, kvm@...r.kernel.org, kvm-riscv@...ts.infradead.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
Andrew Jones <ajones@...tanamicro.com>, James Houghton <jthoughton@...gle.com>,
David Woodhouse <dwmw@...zon.co.uk>, linux-next@...r.kernel.org
Subject: Re: [PATCH v3 03/14] KVM: selftests: Return a value from
vcpu_get_reg() instead of using an out-param
On Fri, Nov 01, 2024, Oliver Upton wrote:
> On Fri, Nov 01, 2024 at 09:16:42AM -0700, Sean Christopherson wrote:
> > One thing I'll add to my workflow would be to do a local merge (and smoke test)
> > of linux-next into kvm-x86 next before pushing it out. This isn't the only snafu
> > this cycle where such a sanity check would have saved me and others a bit of pain.
>
> Eh, shit happens, that's what -next is for :)
Heh, but I also don't actually test -next, which was another snafu (not my fault
this time!) from this cycle[*]. Testing 6.12-next prior to the merge window
wouldn't have made that any less painful to bisect, but I think it would at least
have allowed me to detect that the issue specifically came in from linux-next,
and the bug report would have gotten to PeterZ almost two months earlier.
https://lore.kernel.org/all/ZwdA0sbA2tJA3IKh@google.com
Powered by blists - more mailing lists