From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Gavin Shan <gshan@redhat.com>,
kvmarm <kvmarm@lists.cs.columbia.edu>,
KVM list <kvm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-kselftest <linux-kselftest@vger.kernel.org>,
Florian Weimer <fweimer@redhat.com>,
shan gavin <shan.gavin@gmail.com>, maz <maz@kernel.org>,
andrew jones <andrew.jones@linux.dev>, yihyu <yihyu@redhat.com>,
Sean Christopherson <seanjc@google.com>,
oliver upton <oliver.upton@linux.dev>
Subject: Re: [PATCH v2 1/2] KVM: selftests: Make rseq compatible with glibc-2.35
Date: Wed, 10 Aug 2022 08:30:14 -0400 (EDT) [thread overview]
Message-ID: <264792101.376.1660134614855.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1e41a634-0419-e0a8-364c-2e30ed2dbe4d@redhat.com>
----- On Aug 10, 2022, at 8:29 AM, Paolo Bonzini pbonzini@redhat.com wrote:
> On 8/10/22 14:22, Mathieu Desnoyers wrote:
>>>
>>> /*
>>> * Create and run a dummy VM that immediately exits to userspace via
>>> @@ -256,7 +244,7 @@ int main(int argc, char *argv[])
>>> */
>>> smp_rmb();
>>> cpu = sched_getcpu();
>>> - rseq_cpu = READ_ONCE(__rseq.cpu_id);
>>> + rseq_cpu = READ_ONCE(__rseq->cpu_id);
>> #include <rseq.h>
>>
>> and use
>>
>> rseq_current_cpu_raw().
>
> Thanks, I squashed it and queued it for -rc1 (tested on both
> glibc 2.34 and 2.35).
Thanks a lot Paolo,
Cheers! :)
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2022-08-10 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 10:41 [PATCH v2 0/2] kvm/selftests: Two rseq_test fixes Gavin Shan
2022-08-10 10:41 ` [PATCH v2 1/2] KVM: selftests: Make rseq compatible with glibc-2.35 Gavin Shan
2022-08-10 12:22 ` Mathieu Desnoyers
2022-08-10 12:29 ` Paolo Bonzini
2022-08-10 12:30 ` Mathieu Desnoyers [this message]
2022-08-10 23:57 ` Gavin Shan
2022-08-10 10:41 ` [PATCH v2 2/2] KVM: selftests: Use getcpu() instead of sched_getcpu() in rseq_test Gavin Shan
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=264792101.376.1660134614855.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=andrew.jones@linux.dev \
--cc=fweimer@redhat.com \
--cc=gshan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shan.gavin@gmail.com \
--cc=yihyu@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox