From: Don Porter <porter@cs.unc.edu>
To: Andy Lutomirski <luto@amacapital.net>,
LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
Stas Sergeev <stsp@list.ru>,
linux-sgx@vger.kernel.org
Subject: Re: Linux FSGSBASE testing
Date: Sat, 18 Jul 2020 16:18:06 -0400 [thread overview]
Message-ID: <6e3d25fc-9a67-8655-a00a-b3afbc360ff0@cs.unc.edu> (raw)
In-Reply-To: <CALCETrU_O4AxcJeBO77uXt2j8woYVtjZd18-YV0BuCKRAu00eA@mail.gmail.com>
On 6/20/20 11:59 AM, Andy Lutomirski wrote:
> Hi Stas-
>
> FSGSBASE support is queued up for Linux 5.9. Since you're one of the
> more exotic users of segmentation on Linux, is there any chance you
> could test it? The code is here:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/log/?h=x86/fsgsbase
>
> There are two interesting cases to test:
>
> 1. FSGSBASE on. This is the default if you boot this kernel on Ivy
> Bridge or newer hardware.
>
> 2. FSGSBASE off on a patched kernel. Boot the same kernel as in #1
> but either pass nofsgsbase on the kernel command line or use pre-Ivy
> Bridge hardware. You will *
>
> You can tell you have FSGSBASE enabled for test #1 by running
> tools/testing/selftests/x86/fsgsbase_64 -- the first line of output
> will be :FSGSBASE instructions are enabled". You can build it by
> cd-ing to tools/testing/selftests/x86 and running make.
>
> If anything is broken for you, I'd like to know before this makes it
> into a released kernel!
>
> Thanks,
> Andy
>
FWIW, we tested this patch using Graphene under Case 1, both in our
standard CI pipelines, and with hand testing. Everything looks good on
our end - no suspicious dmesg, no application-level issues.
I also reran the stress test Andy suggested on a separate thread, which
also looks good:
* Graphene running nginx pinned to core 0
* infinite loop on core 0
* perf top running
* Exercised with non-SGX apache bench several times (~10 minutes of
testing time) also from core 0
All the best,
Don
parent reply other threads:[~2020-07-18 20:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CALCETrU_O4AxcJeBO77uXt2j8woYVtjZd18-YV0BuCKRAu00eA@mail.gmail.com>]
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=6e3d25fc-9a67-8655-a00a-b3afbc360ff0@cs.unc.edu \
--to=porter@cs.unc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=stsp@list.ru \
--cc=x86@kernel.org \
/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 NNTP newsgroup(s).