From: Suprateeka R Hegde <hegdesmailbox@gmail.com>
To: Carlos O'Donell <carlos@redhat.com>, "H.J. Lu" <hjl.tools@gmail.com>
Cc: 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: <ea55babe-9848-c5f0-5b79-2c0a835bc401@gmail.com> (raw)
In-Reply-To: <ef10d0ae-9c5e-1a20-eef4-bea29005b1ed@redhat.com>
On 04-Mar-2017 07:37 AM, Carlos O'Donell wrote:
> On 03/03/2017 11:00 AM, H.J. Lu wrote:
>> __gnu_mbind_setup is called from ld.so. Since there is only one ld.so,
>> it needs to know what to pass to __gnu_mbind_setup. Not all arguments
>> have to be used by all implementations nor all memory types.
>
> I think what Supra is suggesting is a pointer-to-implementation interface
> which would allow ld.so to pass completely different arguments to the
> library depending on what kind of memory is being defined by the sh_info
> value. It avoids needing to encode all the types in the API, and just
> uses an incomplete pointer to the type.
Thats absolutely right.
However, I am not suggesting one is better over the other. I just want
to get clarity on how the code looks like for different implementations.
On 03-Mar-2017 09:30 PM, H.J. Lu wrote:
> __gnu_mbind_setup is called from ld.so. Since there is only one ld.so,
> it needs to know what to pass to __gnu_mbind_setup.
So I want to know what is that ONE-FIXED-FORM of __gnu_mbind_setup being
called by ld.so.
> Not all arguments
> have to be used by all implementations nor all memory types.
I think I am still not getting this. Really sorry for that. Would it be
possible for you to write a small pseudo code that depicts how this
design looks like for different implementations?
Thanks a lot
--
Supra
next prev parent reply other threads:[~2017-03-06 13:25 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 ` 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
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 [this message]
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
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=ea55babe-9848-c5f0-5b79-2c0a835bc401@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).