From: Suprateeka R Hegde <hegdesmailbox@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Carlos O'Donell <carlos@redhat.com>, gnu-gabi@sourceware.org
Subject: Re: RFC: ABI support for special memory area
Date: Sun, 01 Jan 2017 00:00:00 -0000 [thread overview]
Message-ID: <35fce20b-20e0-3d0e-1957-f3df124a05ac@gmail.com> (raw)
In-Reply-To: <CAMe9rOqt-9GCH=XdhBpwT0xK_Csu3PSYKAheCn-BnpCXamCjNQ@mail.gmail.com>
On 30-Mar-2017 10:10 PM, H.J. Lu wrote:
>> However, I am just thinking that your earlier approach --
>> __gnu_mbind_setup -- is better when shared libraries with GNU_MBIND
>> segments are dlopen'ed. They dont have to iterate all over again to
>> reach their PHDR. Or what is the recommendation for such dlopen'ed
>> libraries?
>
> It is true that dl_iterate_phdr is called by every shared object, dlopened or
> not, to locate its own PHDR.
Lets put a one liner on best practices or guideline kind of. You have
already made it clear in the example code. I am just thinking of putting
them in words too.
Lets say something like, each load module is expected to process only
its special memory segments. To mean that shlibs/exe need not do any
book-keeping to avoid multiple executions of the special memory setup
for the same load module.
>> And this dl_iterate_phdr(3) not being part of any standards, may change
>> in a totally incompatible way in the future.
>>
>
> dl_iterate_phdr isn't in any standard. But it is in glibc. Given that my
> proposal is a GNU extension, it isn't a major issue. Working with
> existing glibc is a big plus.
Awesome. Looks great. Thanks a lot for the new approach.
--
Supra
next prev parent reply other threads:[~2017-03-31 13:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:00 H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Suprateeka R Hegde [this message]
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` H.J. Lu
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=35fce20b-20e0-3d0e-1957-f3df124a05ac@gmail.com \
--to=hegdesmailbox@gmail.com \
--cc=carlos@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).