Received-SPF: pass (google.com: domain of linux-kernel+bounces-42401-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>, Sean
 Christopherson <seanjc@google.com>
Cc: Oliver Upton <oupton@google.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] KVM: selftests: Fix clocksource requirements in tests
In-Reply-To: <20240109141121.1619463-1-vkuznets@redhat.com>
References: <20240109141121.1619463-1-vkuznets@redhat.com>
Date: Mon, 29 Jan 2024 10:03:56 +0100
Message-ID: <87a5oo8q9v.fsf@redhat.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain

Vitaly Kuznetsov <vkuznets@redhat.com> writes:

> It was discovered that 'hyperv_clock' fails miserably when the system is
> using an unsupported (by KVM) clocksource, e.g. 'kvm-clock'. The root cause
> of the failure is that 'hyperv_clock' doesn't actually check which clocksource
> is currently in use. Other tests (kvm_clock_test, vmx_nested_tsc_scaling_test)
> have the required check but each test does it on its own.
>
> Generalize clocksource checking infrastructure, make all three clocksource
> dependent tests run with 'tsc' and 'hyperv_clocksource_tsc_page', and skip
> gracefully when run in an unsupported configuration.
>
> The last patch of the series is a loosely related minor nitpick for KVM
> code itself.
>
> Vitaly Kuznetsov (5):
>   KVM: selftests: Generalize check_clocksource() from kvm_clock_test
>   KVM: selftests: Use generic sys_clocksource_is_tsc() in
>     vmx_nested_tsc_scaling_test
>   KVM: selftests: Run clocksource dependent tests with
>     hyperv_clocksource_tsc_page too
>   KVM: selftests: Make hyperv_clock require TSC based system clocksource
>   KVM: x86: Make gtod_is_based_on_tsc() return 'bool'

Ping)

-- 
Vitaly