From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Dongjie Zou <zoudongjie@huawei.com>
Subject: Re: [PATCH v2 4/4] KVM: selftests: Add CPUID tests for Hyper-V features that need in-kernel APIC
Date: Tue, 21 Jan 2025 17:29:22 +0100 [thread overview]
Message-ID: <87wmeo6sgt.fsf@redhat.com> (raw)
In-Reply-To: <Z4_Em95xkvagPOHN@google.com>
Sean Christopherson <seanjc@google.com> writes:
> On Mon, Jan 20, 2025, Vitaly Kuznetsov wrote:
>> > diff --git a/tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c b/tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c
>> > index 3188749ec6e1..8f26130dc30d 100644
>> > --- a/tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c
>> > +++ b/tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c
>> > @@ -43,6 +43,7 @@ static bool smt_possible(void)
>> >
>> > static void test_hv_cpuid(struct kvm_vcpu *vcpu, bool evmcs_expected)
>> > {
>> > + const bool has_irqchip = !vcpu || vcpu->vm->has_irqchip;
>> > const struct kvm_cpuid2 *hv_cpuid_entries;
>> > int i;
>> > int nent_expected = 10;
>> > @@ -85,12 +86,19 @@ static void test_hv_cpuid(struct kvm_vcpu *vcpu, bool evmcs_expected)
>> > entry->eax, evmcs_expected
>> > );
>> > break;
>> > + case 0x40000003:
>> > + TEST_ASSERT(has_irqchip || !(entry->edx & BIT(19)),
>> > + "Synthetic Timers should require in-kernel APIC");
>>
>> Nitpick: BIT(19) of CPUID.0x40000003(EDX) advertises 'direct' mode
>> for Synthetic timers and that's what we have paired with
>> lapic_in_kernel() check. Thus, we may want to be a bit more specific and
>> say
>>
>> "Direct Synthetic timers should require in-kernel APIC"
>> (personally, I'd prefer "Synthetic timers in 'direct' mode" name but
>> that's not how TLFS calls them)
>
> What about adding quotes to try and communicate that it's a property of Syntehtic
> Timers? E.g.
>
> "\"Direct\" Synthetic Timers should require in-kernel APIC");
Sounds good to me)
--
Vitaly
next prev parent reply other threads:[~2025-01-21 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 0:34 [PATCH v2 0/4] KVM: x86: Hyper-V SEND_IPI fix and partial testcase Sean Christopherson
2025-01-18 0:34 ` [PATCH v2 1/4] KVM: x86: Reject Hyper-V's SEND_IPI hypercalls if local APIC isn't in-kernel Sean Christopherson
2025-01-18 0:34 ` [PATCH v2 2/4] KVM: selftests: Mark test_hv_cpuid_e2big() static in Hyper-V CPUID test Sean Christopherson
2025-01-18 0:34 ` [PATCH v2 3/4] KVM: selftests: Manage CPUID array in Hyper-V CPUID test's core helper Sean Christopherson
2025-01-20 14:20 ` Vitaly Kuznetsov
2025-01-18 0:34 ` [PATCH v2 4/4] KVM: selftests: Add CPUID tests for Hyper-V features that need in-kernel APIC Sean Christopherson
2025-01-20 14:20 ` Vitaly Kuznetsov
2025-01-21 16:00 ` Sean Christopherson
2025-01-21 16:29 ` Vitaly Kuznetsov [this message]
2025-02-15 0:50 ` [PATCH v2 0/4] KVM: x86: Hyper-V SEND_IPI fix and partial testcase Sean Christopherson
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=87wmeo6sgt.fsf@redhat.com \
--to=vkuznets@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=zoudongjie@huawei.com \
/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.