Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) client-ip=2620:137:e000::3:2;
MIME-Version: 1.0
References: <20231013234808.1115781-1-seanjc@google.com> <20231013234808.1115781-2-seanjc@google.com>
In-Reply-To: <20231013234808.1115781-2-seanjc@google.com>
From:   Paolo Bonzini <pbonzini@redhat.com>
Date:   Sun, 15 Oct 2023 14:25:38 +0200
Message-ID: <CABgObfZOb1sV1LZpXR0=L-CG6ZPnxL37=zhdOk4zpcKxmVgMjw@mail.gmail.com>
Subject: Re: [GIT PULL] KVM: x86: Selftests fixes for 6.6
To:     Sean Christopherson <seanjc@google.com>
Cc:     kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Sat, Oct 14, 2023 at 1:48=E2=80=AFAM Sean Christopherson <seanjc@google.=
com> wrote:
>
> Please pull a fix, a cleanup, and a workaround for 6.6.  The guest printf=
 change
> really should go into 6.6, as it fixes an issue introduced in 6.6 that ca=
uses
> affected guest asserts to print garbage.  The other two changes are much =
less
> urgent, but I couldn't think of a any reason to hold them back.

The printf one I had already applied, but the double commit is not a huge i=
ssue.

Pulled, thanks.

Paolo

> The following changes since commit 5804c19b80bf625c6a9925317f845e497434d6=
d3:
>
>   Merge tag 'kvm-riscv-fixes-6.6-1' of https://github.com/kvm-riscv/linux=
 into HEAD (2023-09-23 05:35:55 -0400)
>
> are available in the Git repository at:
>
>   https://github.com/kvm-x86/linux.git tags/kvm-x86-selftests-6.6-fixes
>
> for you to fetch changes up to 6313e096dbfaf1377ba8f5f8ccd720cc36c576c6:
>
>   KVM: selftests: Zero-initialize entire test_result in memslot perf test=
 (2023-10-05 19:23:47 -0700)
>
> ----------------------------------------------------------------
> KVM selftests fixes for 6.6:
>
>  - Play nice with %llx when formatting guest printf and assert statements=
.
>
>  - Clean up stale test metadata.
>
>  - Zero-initialize structures in memslot perf test to workaround a suspec=
ted
>    "may be used uninitialized" false positives from GCC.
>
> ----------------------------------------------------------------
> Like Xu (1):
>       KVM: selftests: Remove obsolete and incorrect test case metadata
>
> Sean Christopherson (2):
>       KVM: selftests: Treat %llx like %lx when formatting guest printf
>       KVM: selftests: Zero-initialize entire test_result in memslot perf =
test
>
>  tools/testing/selftests/kvm/include/ucall_common.h       | 2 --
>  tools/testing/selftests/kvm/lib/guest_sprintf.c          | 7 +++++++
>  tools/testing/selftests/kvm/lib/x86_64/apic.c            | 2 --
>  tools/testing/selftests/kvm/memslot_perf_test.c          | 9 +++------
>  tools/testing/selftests/kvm/x86_64/hyperv_svm_test.c     | 2 --
>  tools/testing/selftests/kvm/x86_64/nx_huge_pages_test.c  | 2 --
>  tools/testing/selftests/kvm/x86_64/nx_huge_pages_test.sh | 1 -
>  tools/testing/selftests/kvm/x86_64/tsc_scaling_sync.c    | 4 ----
>  tools/testing/selftests/kvm/x86_64/xen_shinfo_test.c     | 4 ----
>  9 files changed, 10 insertions(+), 23 deletions(-)
>