Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 29 May 2020 17:27:56 +0200
From:   Wojtek Porczyk <woju@invisiblethingslab.com>
To:     Andy Lutomirski <luto@amacapital.net>
Cc:     Don Porter <porter@cs.unc.edu>,
        Thomas Gleixner <tglx@linutronix.de>,
        Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
        Andi Kleen <ak@linux.intel.com>,
        Sasha Levin <sashal@kernel.org>, linux-kernel@vger.kernel.org,
        bp@alien8.de, luto@kernel.org, hpa@zytor.com,
        dave.hansen@intel.com, tony.luck@intel.com,
        ravi.v.shankar@intel.com, chang.seok.bae@intel.com
Subject: Re: [PATCH v12 00/18] Enable FSGSBASE instructions
Message-ID: <20200529152756.GA7452@invisiblethingslab.com>
Mail-Followup-To: Andy Lutomirski <luto@amacapital.net>,
        Don Porter <porter@cs.unc.edu>,
        Thomas Gleixner <tglx@linutronix.de>,
        Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
        Andi Kleen <ak@linux.intel.com>, Sasha Levin <sashal@kernel.org>,
        linux-kernel@vger.kernel.org, bp@alien8.de, luto@kernel.org,
        hpa@zytor.com, dave.hansen@intel.com, tony.luck@intel.com,
        ravi.v.shankar@intel.com, chang.seok.bae@intel.com
References: <e9a0a521-104b-5c3a-a689-78f878e73d31@cs.unc.edu>
 <7A3EBAB0-B3B3-4CB7-AA6A-FDF29D03E30D@amacapital.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP"
Content-Disposition: inline
In-Reply-To: <7A3EBAB0-B3B3-4CB7-AA6A-FDF29D03E30D@amacapital.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


--5mCyUwZo2JvN/JJP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, May 28, 2020 at 11:38:01AM -0700, Andy Lutomirski wrote:
> One useful test for the actual kernel patches would be to run your SGX
> workload on a loaded core.  That is, do something like taskset -c
> 0 graphene_thing and, simultaneously, write a trivial infinite loop progr=
am
> and run that under taskset -c 0 as well. For good measure, you could have
> perf top or perf record running at the same time.  Look for kernel errors,
> but also look for any evidence of your workload malfunctioning.

We currently run as part of CI several workloads[1], among them LTP tests[2=
],
and sometimes it's not pretty, because we encounter stability problems in
Graphene+SGX even without the patchset. We'll pick some stable subset and
will let know. Right now we'll have to retool CI for custom kernels, which
will take some back and forth with uni's admins.

[1] https://github.com/oscarlab/graphene/tree/master/Examples
[2] https://github.com/oscarlab/graphene/tree/master/LibOS/shim/test/ltp

--=20
pozdrawiam / best regards
Wojtek Porczyk
Graphene / Invisible Things Lab
=20
 I do not fear computers,
 I fear lack of them.
    -- Isaac Asimov

--5mCyUwZo2JvN/JJP
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEaO0VFfpr0tEF6hYkv2vZMhA6I1EFAl7RKfsACgkQv2vZMhA6
I1FwkBAAj6TLkpFQtU7aEJEyWCxLeXiB+5+9Tt/q9/AO25+Za/CPrYmAGLPxGre8
O/MQfe1XfeniHbzPDUKKBxv4/dDfyan+Xmzbm/g9G/S8xeDeGi4p9VpHEj2OOnHg
lpM0MNPO2b5XejdhOXIppq+dvx/Kp8cVscLp8KOxO2/zcqRW0PjMjmTcQS9aaG4o
r6nuAd6oFctztYdEUqExVrg8G3zgYOGyVxtRydlpunGtbahDuZH2+cqS314nB86b
8y3gGyeUhTGiMTpj765yKk8bRMisv8MtUFfzCJHjzPVufuL40xRwGVL32J6Oy22e
xq9PKdcS92wBKH6IMuyqOVg6BU6wyV03douNfGuHQNqs1jVjc/k+33fwbklc/AIW
xDxh9cypR2WagVWnE5+j1cHq7n132sD3D/bV0l3t/FUTP/fKjSuke+Uz7czfIi4L
O6QmVlzotC7tatZUt17INpO3ycv7EjYmh0p/yObVu88ovPNGu6IPzo3p72y2sCTj
dWJWKqn0jFGi6maSrsdZag8Fl1YkaLjO4EH4YpGQNckhYZwhZTqg0+w+LF6lKfQ6
cC3DppUiDM/HwKa560cBWMuKfzZ2leGAcoXIl2SkBd1iyM06Yq45CVvjxyQ9wgUp
cuTLgQ/TsosJT3ToGw5cscMt3oKE5fSnucrJRVRRCfy/kiH49y8=
=fSib
-----END PGP SIGNATURE-----

--5mCyUwZo2JvN/JJP--