From: jarkko.sakkinen at linux.intel.com (Jarkko Sakkinen)
Subject: [PATCH RFC] selftests/x86: Add a selftest for SGX
Date: Thu, 15 Nov 2018 22:33:56 +0200 [thread overview]
Message-ID: <20181115203356.GC26875@linux.intel.com> (raw)
In-Reply-To: <ace87d75-2ba0-38f6-0a77-25d45b692d7d@intel.com>
On Tue, Nov 13, 2018 at 01:51:06PM -0800, Dave Hansen wrote:
> On 11/13/18 1:40 PM, Jarkko Sakkinen wrote:
> > +int main(int argc, char **argv)
> > +{
> > + unsigned long bin_size = (unsigned long)&encl_bin_end -
> > + (unsigned long)&encl_bin;
> > + struct sgx_secs secs;
> > + uint64_t result = 0;
> > +
> > + if (!encl_load(&secs, bin_size))
> > + exit(1);
> > +
> > + sgx_call((void *)&MAGIC, &result, (void *)secs.base);
> > + if (result != MAGIC) {
> > + fprintf(stderr, "0x%lx != 0x%lx\n", result, MAGIC);
> > + exit(1);
> > + }
> > +
> > + exit(0);
> > +}
>
> Well, I guess 100 lines of code for something a wee bit shy of hello
> world isn't bad. :)
>
> In general, this looks fine, but probably needs some better commenting
> and probably some messages that make it a bit more clear what is going on.
>
> It would be _nice_, for instance to try to do some CPUID detection of
> SGX so that the error (or success?) message can tell you whether you're
> missing hardware support or kernel support.
>
> Thanks for doing this, though. It's sorely needed.
Great, thanks, I see what I can do.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
Subject: [PATCH RFC] selftests/x86: Add a selftest for SGX
Date: Thu, 15 Nov 2018 22:33:56 +0200 [thread overview]
Message-ID: <20181115203356.GC26875@linux.intel.com> (raw)
Message-ID: <20181115203356.Y_jWT5jt0lHma2dFEMNMBnxmOHzQtbosFqMpweWN9EE@z> (raw)
In-Reply-To: <ace87d75-2ba0-38f6-0a77-25d45b692d7d@intel.com>
On Tue, Nov 13, 2018@01:51:06PM -0800, Dave Hansen wrote:
> On 11/13/18 1:40 PM, Jarkko Sakkinen wrote:
> > +int main(int argc, char **argv)
> > +{
> > + unsigned long bin_size = (unsigned long)&encl_bin_end -
> > + (unsigned long)&encl_bin;
> > + struct sgx_secs secs;
> > + uint64_t result = 0;
> > +
> > + if (!encl_load(&secs, bin_size))
> > + exit(1);
> > +
> > + sgx_call((void *)&MAGIC, &result, (void *)secs.base);
> > + if (result != MAGIC) {
> > + fprintf(stderr, "0x%lx != 0x%lx\n", result, MAGIC);
> > + exit(1);
> > + }
> > +
> > + exit(0);
> > +}
>
> Well, I guess 100 lines of code for something a wee bit shy of hello
> world isn't bad. :)
>
> In general, this looks fine, but probably needs some better commenting
> and probably some messages that make it a bit more clear what is going on.
>
> It would be _nice_, for instance to try to do some CPUID detection of
> SGX so that the error (or success?) message can tell you whether you're
> missing hardware support or kernel support.
>
> Thanks for doing this, though. It's sorely needed.
Great, thanks, I see what I can do.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: x86@kernel.org, platform-driver-x86@vger.kernel.org,
linux-sgx@vger.kernel.org, sean.j.christopherson@intel.com,
nhorman@redhat.com, npmccallum@redhat.com, serge.ayoun@intel.com,
shay.katz-zamir@intel.com, haitao.huang@intel.com,
andriy.shevchenko@linux.intel.com, tglx@linutronix.de,
kai.svahn@intel.com, Shuah Khan <shuah@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Andy Lutomirski <luto@kernel.org>,
Dmitry Safonov <dima@arista.com>,
Florian Weimer <fweimer@redhat.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Suresh Siddha <suresh.b.siddha@intel.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH RFC] selftests/x86: Add a selftest for SGX
Date: Thu, 15 Nov 2018 22:33:56 +0200 [thread overview]
Message-ID: <20181115203356.GC26875@linux.intel.com> (raw)
In-Reply-To: <ace87d75-2ba0-38f6-0a77-25d45b692d7d@intel.com>
On Tue, Nov 13, 2018 at 01:51:06PM -0800, Dave Hansen wrote:
> On 11/13/18 1:40 PM, Jarkko Sakkinen wrote:
> > +int main(int argc, char **argv)
> > +{
> > + unsigned long bin_size = (unsigned long)&encl_bin_end -
> > + (unsigned long)&encl_bin;
> > + struct sgx_secs secs;
> > + uint64_t result = 0;
> > +
> > + if (!encl_load(&secs, bin_size))
> > + exit(1);
> > +
> > + sgx_call((void *)&MAGIC, &result, (void *)secs.base);
> > + if (result != MAGIC) {
> > + fprintf(stderr, "0x%lx != 0x%lx\n", result, MAGIC);
> > + exit(1);
> > + }
> > +
> > + exit(0);
> > +}
>
> Well, I guess 100 lines of code for something a wee bit shy of hello
> world isn't bad. :)
>
> In general, this looks fine, but probably needs some better commenting
> and probably some messages that make it a bit more clear what is going on.
>
> It would be _nice_, for instance to try to do some CPUID detection of
> SGX so that the error (or success?) message can tell you whether you're
> missing hardware support or kernel support.
>
> Thanks for doing this, though. It's sorely needed.
Great, thanks, I see what I can do.
/Jarkko
next prev parent reply other threads:[~2018-11-15 20:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 21:40 [PATCH RFC] selftests/x86: Add a selftest for SGX jarkko.sakkinen
2018-11-13 21:40 ` Jarkko Sakkinen
2018-11-13 21:40 ` Jarkko Sakkinen
2018-11-13 21:40 ` Jarkko Sakkinen
2018-11-13 21:51 ` dave.hansen
2018-11-13 21:51 ` Dave Hansen
2018-11-13 21:51 ` Dave Hansen
2018-11-15 20:33 ` jarkko.sakkinen [this message]
2018-11-15 20:33 ` Jarkko Sakkinen
2018-11-15 20:33 ` Jarkko Sakkinen
2018-11-14 16:09 ` sean.j.christopherson
2018-11-14 16:09 ` Sean Christopherson
2018-11-14 16:09 ` Sean Christopherson
2018-11-15 20:37 ` jarkko.sakkinen
2018-11-15 20:37 ` Jarkko Sakkinen
2018-11-15 20:37 ` Jarkko Sakkinen
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=20181115203356.GC26875@linux.intel.com \
--to=unknown@example.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.