The TODO about using the number of vCPUs instead of vcpu.id + 1
was already addressed by commit 376bc1b458c9 ("KVM: selftests: Don't
assume vcpu->id is '0' in xAPIC state test"). The comment is now
stale and can be removed.

Signed-off-by: Sukrut Heroorkar <hsukr...@gmail.com>
---
 tools/testing/selftests/kvm/x86/xapic_state_test.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/testing/selftests/kvm/x86/xapic_state_test.c 
b/tools/testing/selftests/kvm/x86/xapic_state_test.c
index fdebff1165c7..3b4814c55722 100644
--- a/tools/testing/selftests/kvm/x86/xapic_state_test.c
+++ b/tools/testing/selftests/kvm/x86/xapic_state_test.c
@@ -120,8 +120,8 @@ static void test_icr(struct xapic_vcpu *x)
                __test_icr(x, icr | i);
 
        /*
-        * Send all flavors of IPIs to non-existent vCPUs.  TODO: use number of
-        * vCPUs, not vcpu.id + 1.  Arbitrarily use vector 0xff.
+        * Send all flavors of IPIs to non-existent vCPUs. Arbitrarily use
+        * vector 0xff.
         */
        icr = APIC_INT_ASSERT | 0xff;
        for (i = 0; i < 0xff; i++) {
-- 
2.43.0


Reply via email to