[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y1vxncv1.fsf@oldenburg.str.redhat.com>
Date: Tue, 09 Aug 2022 08:35:14 +0200
From: Florian Weimer <fweimer@...hat.com>
To: Gavin Shan <gshan@...hat.com>
Cc: kvmarm@...ts.cs.columbia.edu, kvm@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
pbonzini@...hat.com, maz@...nel.org, oliver.upton@...ux.dev,
andrew.jones@...ux.dev, seanjc@...gle.com,
mathieu.desnoyers@...icios.com, yihyu@...hat.com,
shan.gavin@...il.com
Subject: Re: [PATCH 2/2] KVM: selftests: Use getcpu() instead of
sched_getcpu() in rseq_test
* Gavin Shan:
> sched_getcpu() is glibc dependent and it can simply return the CPU
> ID from the registered rseq information, as Florian Weimer pointed.
> In this case, it's pointless to compare the return value from
> sched_getcpu() and that fetched from the registered rseq information.
>
> Fix the issue by replacing sched_getcpu() with getcpu(), as Florian
> suggested. The comments are modified accordingly.
Note that getcpu was added in glibc 2.29, so perhaps you need to perform
a direct system call?
Thanks,
Florian
Powered by blists - more mailing lists