[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f399a68a-ad9d-4734-b5da-25f5ce3b832e@sirena.org.uk>
Date: Wed, 28 Feb 2024 21:38:35 +0000
From: Mark Brown <broonie@...nel.org>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Thomas Huth <thuth@...hat.com>, kvm@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
Paolo Bonzini <pbonzini@...hat.com>,
Andrew Jones <ajones@...tanamicro.com>,
Marc Zyngier <maz@...nel.org>,
Oliver Upton <oliver.upton@...ux.dev>,
Aishwarya TCV <aishwarya.tcv@....com>
Subject: Re: [PATCH v3 3/8] KVM: selftests: Move setting a vCPU's entry point
to a dedicated API
On Wed, Feb 28, 2024 at 01:19:48PM -0800, Sean Christopherson wrote:
> I'll squash the above and force push.
Thanks, I'll give that a spin (likely tomorrow at this point).
> And another question: is there any reason to not force -Werror for selftests?
Enabling it by default can cause a bunch of fragility when people are
running different compilers, there's things like all the different clang
versions, and it's especially common to run into issues when you've got
a shiny new compiler on a modern distro but need to go look at older
kernels for some reason. You then get issues bisecting things since you
get regions where the build was broken due to -Werror which may or may
not be pointing at the runtime issue you were looking for (particularly
likely to be hiding things if the build issue is in a different test).
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists