From: Suprateeka R Hegde <hegdesmailbox@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.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: <ee7a8072-08a5-3efc-dffb-fd0ab504e1d6@gmail.com> (raw)
In-Reply-To: <CAMe9rOrwm=U9891moSKLQEtbtLMTibFfh5Ok05YjMG_bJj7rJw@mail.gmail.com>
On 23-Feb-2017 09:49 PM, H.J. Lu wrote:
> The default implementation of __gnu_mbind_setup is
>
> int
> __gnu_mbind_setup (unsigned int type, void *addr, size_t length)
> {
> return 0;
> }
>
> which can be overridden by a different implementation at link-time.
>
Since this is a design that allows vendor specific extension and
implementation, would it OK if we make it more generic?
Instead of a fixed 3 arguments (type, addr, len), how about something
like a pointer to a generic MBIND_CONTEXT struct (say of type
__gnu_mbind_context defined)? And let the implementation define the
actual struct.
I would like to handle NVM/NVMe (long back I had mentioned about
PT_PERSISTENT) through this MBIND and my implementation of handling
NVM/NVMe needs more data to be passed to such "setup" functions.
Or is this __gnu_mbind_setup should be considered as a very basic /
fundamental function (used just to setup the "memory area") and
implementations/vendors are expected to write wrapper/handler functions
to handle other aspects of the special memory? In that case the fixed
set of basic args looks OK.
IMHO this __gnu_mbind_setup is a very good design to be generic enough
and not be very specific/basic/fundamental runtime support.
--
Supra
next prev parent reply other threads:[~2017-03-02 15:17 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 [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 ` 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 ` 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
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 ` 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=ee7a8072-08a5-3efc-dffb-fd0ab504e1d6@gmail.com \
--to=hegdesmailbox@gmail.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).