From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: carlos <carlos@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
libc-alpha <libc-alpha@sourceware.org>,
Thomas Gleixner <tglx@linutronix.de>, Ben Maurer <bmaurer@fb.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Boqun Feng <boqun.feng@gmail.com>,
Will Deacon <will.deacon@arm.com>,
Dave Watson <davejwatson@fb.com>, Paul Turner <pjt@google.com>,
Rich Felker <dalias@libc.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-api <linux-api@vger.kernel.org>
Subject: Re: [PATCH 1/5] glibc: Perform rseq(2) registration at C startup and thread creation (v10)
Date: Fri, 14 Jun 2019 06:14:09 -0400 (EDT) [thread overview]
Message-ID: <1635690189.3049.1560507249693.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <87ftocwkei.fsf@oldenburg2.str.redhat.com>
----- On Jun 14, 2019, at 12:06 PM, Florian Weimer fweimer@redhat.com wrote:
> * Mathieu Desnoyers:
>
>> ----- On Jun 12, 2019, at 4:00 PM, Mathieu Desnoyers
>> mathieu.desnoyers@efficios.com wrote:
>>
>>> ----- On Jun 10, 2019, at 4:43 PM, carlos carlos@redhat.com wrote:
>>>
>>>> On 6/6/19 7:57 AM, Florian Weimer wrote:
>>>>> Let me ask the key question again: Does it matter if code observes the
>>>>> rseq area first without kernel support, and then with kernel support?
>>>>> If we don't expect any problems immediately, we do not need to worry
>>>>> much about the constructor ordering right now. I expect that over time,
>>>>> fixing this properly will become easier.
>>>>
>>>> I just wanted to chime in and say that splitting this into:
>>>>
>>>> * Ownership (__rseq_handled)
>>>>
>>>> * Initialization (__rseq_abi)
>>>>
>>>> Makes sense to me.
>>>>
>>>> I agree we need an answer to this question of ownership but not yet
>>>> initialized, to owned and initialized.
>>>>
>>>> I like the idea of having __rseq_handled in ld.so.
>>>
>>> Very good, so I'll implement this approach. Sorry for the delayed
>>> feedback, I am traveling this week.
>>
>> I had issues with cases where application or LD_PRELOAD library also
>> define the __rseq_handled symbol. They appear not to see the same
>> address as the one initialized by ld.so.
>
> What exactly did you do? How did you determine the addresses? How is
> __rseq_handled defined in ld.so?
The easiest way to answer these questions is through links to my github
dev branch:
https://github.com/compudj/glibc-dev/tree/glibc-rseq
specifically this commit:
https://github.com/compudj/glibc-dev/commit/c49a286497d065a7fc00aafd846e6edce14f97fc
and this attempt at using GL():
https://github.com/compudj/glibc-dev/commit/8a02acfbb6943672bfa36b4fc6f61905ee4fa180
My test programs are:
* a.c:
#include <stdio.h>
#include <linux/rseq.h>
extern __thread struct rseq __rseq_abi
__attribute__ ((tls_model ("initial-exec")));/* = {
.cpu_id = -1,
};*/
extern int __rseq_handled;
int main()
{
fprintf(stderr, "__rseq_handled main: %d %p\n", __rseq_handled, &__rseq_handled);
fprintf(stderr, "__rseq_abi.cpu_id main: %d %p\n", __rseq_abi.cpu_id, &__rseq_abi);
return 0;
}
* s.c:
#include <stdio.h>
#include <linux/rseq.h>
#if 0
__thread struct rseq __rseq_abi
__attribute__ ((tls_model ("initial-exec"))) = {
.cpu_id = -1,
};
int __rseq_handled;
#else
extern __thread struct rseq __rseq_abi
__attribute__ ((tls_model ("initial-exec")));
extern int __rseq_handled;
#endif
void __attribute__((constructor)) myinit(void)
{
fprintf(stderr, "__rseq_handled s.so: %d %p\n", __rseq_handled, &__rseq_handled);
fprintf(stderr, "__rseq_abi.cpu_id s.so: %d %p\n", __rseq_abi.cpu_id, &__rseq_abi);
}
* Makefile:
LIBCPATH=/home/efficios/glibc-test/lib
KERNEL_HEADERS=/home/efficios/git/linux-percpu-dev/usr/include
CFLAGS=-I${KERNEL_HEADERS} -L${LIBCPATH} -Wl,--rpath=${LIBCPATH} -Wl,--dynamic-linker=${LIBCPATH}/ld-linux-x86-64.so.2
all:
gcc ${CFLAGS} -o a a.c
gcc ${CFLAGS} -shared -fPIC -o s.so s.c
Thanks,
Mathieu
>
> Thanks,
> Florian
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2019-06-14 10:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190503184219.19266-1-mathieu.desnoyers@efficios.com>
2019-05-03 18:42 ` [PATCH 1/5] glibc: Perform rseq(2) registration at C startup and thread creation (v10) Mathieu Desnoyers
2019-05-27 11:19 ` Florian Weimer
2019-05-27 19:27 ` Mathieu Desnoyers
2019-05-29 15:45 ` Mathieu Desnoyers
2019-05-30 20:56 ` Mathieu Desnoyers
2019-05-31 8:06 ` Florian Weimer
2019-05-31 14:48 ` Mathieu Desnoyers
2019-05-31 15:46 ` Florian Weimer
2019-05-31 18:10 ` Mathieu Desnoyers
2019-06-04 11:46 ` Florian Weimer
2019-06-04 15:57 ` Mathieu Desnoyers
2019-06-06 11:57 ` Florian Weimer
2019-06-10 14:43 ` Carlos O'Donell
2019-06-12 14:00 ` Mathieu Desnoyers
2019-06-14 10:03 ` Mathieu Desnoyers
2019-06-14 10:06 ` Florian Weimer
2019-06-14 10:14 ` Mathieu Desnoyers [this message]
2019-06-14 11:35 ` Florian Weimer
2019-06-14 12:55 ` Mathieu Desnoyers
2019-06-14 13:01 ` Mathieu Desnoyers
2019-06-14 13:09 ` Florian Weimer
2019-06-14 13:18 ` Mathieu Desnoyers
2019-06-14 13:24 ` Florian Weimer
2019-06-14 13:34 ` Mathieu Desnoyers
2019-06-14 13:42 ` Florian Weimer
2019-06-14 13:47 ` Mathieu Desnoyers
2019-06-14 13:53 ` Florian Weimer
2019-06-14 13:59 ` Mathieu Desnoyers
2019-06-14 13:29 ` David Laight
2019-06-14 13:39 ` Mathieu Desnoyers
2019-06-12 14:16 ` Mathieu Desnoyers
2019-06-12 14:22 ` Florian Weimer
2019-06-12 14:36 ` Mathieu Desnoyers
2019-06-12 14:43 ` Florian Weimer
2019-05-03 18:42 ` [PATCH 2/5] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux (v4) Mathieu Desnoyers
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=1635690189.3049.1560507249693.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=bmaurer@fb.com \
--cc=boqun.feng@gmail.com \
--cc=carlos@redhat.com \
--cc=dalias@libc.org \
--cc=davejwatson@fb.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=szabolcs.nagy@arm.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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.