From: Jethro Beekman <jethro@fortanix.com>
To: "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>
Subject: Bug in EPC paging
Date: Sat, 27 Jul 2019 23:16:01 +0000 [thread overview]
Message-ID: <b1b95c9c-9191-64d4-37f3-7741cbb0c157@fortanix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
A user is reporting CPU soft lockup with Intel SDK version 2.1 and 2.5
driver. This only happens when using SGX in conjunction with DPDK (Data
Plane Development Kit) in the same process. The process is running two
enclaves that together are bigger than the EPC.
Dmesg output:
2.1 driver:
https://github.com/YangZhou1997/dpdk-sgx-crash/blob/master/dmesg-full.log
2.5 driver:
https://github.com/YangZhou1997/dpdk-sgx-crash/blob/master/dmesg-full-2.5.0.log
Enclave memory layout:
https://github.com/YangZhou1997/dpdk-sgx-crash/blob/master/sgxs.info
--
Jethro Beekman | Fortanix
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3990 bytes --]
next reply other threads:[~2019-07-27 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 23:16 Jethro Beekman [this message]
2019-07-29 14:56 ` Bug in EPC paging Sean Christopherson
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=b1b95c9c-9191-64d4-37f3-7741cbb0c157@fortanix.com \
--to=jethro@fortanix.com \
--cc=linux-sgx@vger.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).