From: Ivana Vukotic <ivanatodvuk@gmail.com>
To: nicolas.ojeda.bar@lexifi.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml and SGX
Date: Thu, 11 Oct 2018 16:02:45 +0200 [thread overview]
Message-ID: <CAE-ccOzQxOLazmPzEALJ66hCCKE+wjx1BhLkXH8q2XyoOBunbw@mail.gmail.com> (raw)
In-Reply-To: <CADK7aFNkYiUuMGvrx296KF9EEfSoG9UbxLL-9Yj1hNSAHqtzeA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2411 bytes --]
Dear Nicolas,
The call to caml_startup can be find in Enclave/Enclave.c
Best regards,
Ivana
On Thu, Oct 11, 2018 at 1:59 PM Nicolás Ojeda Bär <
nicolas.ojeda.bar@lexifi.com> wrote:
> Dear Ivana,
>
> There doesn't seem to be any call to caml_startup in the code you posted.
>
> Regards,
> Nicolás
> On Thu, Oct 11, 2018 at 1:52 PM Ivana Vukotic <ivanatodvuk@gmail.com>
> wrote:
> >
> > Dera Nicolas,
> >
> > Thank you for your suggestion!
> >
> > Actually I already posted the same question with code on the github:
> > https://github.com/intel/linux-sgx/issues/315
> >
> >
> > Best,
> > Ivana
> >
> >
> > On Thu, Oct 11, 2018 at 1:42 PM Nicolás Ojeda Bär <
> nicolas.ojeda.bar@lexifi.com> wrote:
> >>
> >> Dear Ivana,
> >>
> >> You may get more people willing to help if you put up the simple
> >> example somewhere publicly accessible, such as github.
> >>
> >> Best wishes,
> >> Nicolás
> >> On Tue, Oct 9, 2018 at 6:23 PM Ivana Vukotic <ivanatodvuk@gmail.com>
> wrote:
> >> >
> >> > Hi,
> >> >
> >> > We are trying to run some OCaml code within an Intel SGX enclave.
> >> >
> >> > This OCaml code is called by a C wrapper using the method described
> >> > here: https://caml.inria.fr/pub/docs/manual-ocaml/intfc.html
> >> >
> >> > Because Intel SGX doesn't support the entire standard C library, we
> had
> >> > to create ocalls for the functions that are used by ocamlrun but not
> >> > supported by SGX. Using the functionalities provided by Intel SGX, we
> >> > managed to create an .so library containing our OCaml code along with
> >> > the C wrapper. This .so library is what is meant to run in an SGX
> >> > enclave (we so far only implemented the ocalls that we needed, and not
> >> > all missing functionalities from ocamlrun).
> >> >
> >> > Our problem is now that when we call caml_startup from within our C
> >> > wrapper (in order to start the OCaml code), the code seem to simply
> call
> >> > 'exit' and stop there. Does anyone know why this call to caml_startup
> >> > would call 'exit'?
> >> >
> >> > We managed to create a simple example, which I can forward to anyone
> interested
> >> > to take a look (unfortunately mailing list has a limited attachment
> and I can not
> >> > send it).
> >> >
> >> > Please note that we use ocaml 4.06.1 and gcc 7.3.0
> >> >
> >> > Best,
> >> >
> >> > Ivana
>
[-- Attachment #2: Type: text/html, Size: 3612 bytes --]
prev parent reply other threads:[~2018-10-11 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 16:23 Ivana Vukotic
[not found] ` <CADK7aFNPm640fvH9CiE=fczqm-3i5FRsoqmAatoFA+LtohF6AA@mail.gmail.com>
2018-10-11 11:51 ` Ivana Vukotic
2018-10-11 11:59 ` Nicolás Ojeda Bär
2018-10-11 14:02 ` Ivana Vukotic [this message]
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=CAE-ccOzQxOLazmPzEALJ66hCCKE+wjx1BhLkXH8q2XyoOBunbw@mail.gmail.com \
--to=ivanatodvuk@gmail.com \
--cc=caml-list@inria.fr \
--cc=nicolas.ojeda.bar@lexifi.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