From: Jarkko Sakkinen <jarkko@kernel.org>
To: vijay.dhanraj@intel.com
Cc: linux-sgx@vger.kernel.org, reinette.chatre@intel.com,
dave.hansen@linux.intel.com, haitao.huang@intel.com
Subject: Re: [PATCH] Add SGX selftest `augment_via_eaccept_long`
Date: Mon, 8 Aug 2022 15:18:21 +0300 [thread overview]
Message-ID: <YvD/DUGRBR2Tns88@kernel.org> (raw)
In-Reply-To: <20220804201456.33418-1-vijay.dhanraj@intel.com>
On Thu, Aug 04, 2022 at 01:14:56PM -0700, vijay.dhanraj@intel.com wrote:
> From: Vijay Dhanraj <vijay.dhanraj@intel.com>
>
> This commit adds a new test case which is same as `augment_via_eaccept`
> but adds more number of EPC pages to stress test `EAUG` via `EACCEPT`.
>
> Signed-off-by: Vijay Dhanraj <vijay.dhanraj@intel.com>
> Signed-off-by: Haitao Huang <haitao.huang@linux.intel.com>
Hey, to reproduce the original issue: does it reproduce on VM or
should I run baremetal kernel?
BR, Jarkko
next prev parent reply other threads:[~2022-08-08 12:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 20:14 [PATCH] Add SGX selftest `augment_via_eaccept_long` vijay.dhanraj
2022-08-06 18:18 ` Jarkko Sakkinen
2022-08-08 12:18 ` Jarkko Sakkinen [this message]
2022-08-08 13:00 ` Dhanraj, Vijay
2022-08-08 15:29 ` Jarkko Sakkinen
2022-08-09 10:45 ` Jarkko Sakkinen
2022-08-09 16:09 ` Jarkko Sakkinen
2022-08-09 17:08 ` Dhanraj, Vijay
2022-08-09 18:53 ` Jarkko Sakkinen
2022-08-09 18:57 ` Jarkko Sakkinen
2022-08-10 0:09 ` Dhanraj, Vijay
2022-08-11 1:01 ` Jarkko Sakkinen
2022-08-11 1:36 ` Jarkko Sakkinen
2022-08-11 1:50 ` Jarkko Sakkinen
2022-08-11 2:01 ` Dhanraj, Vijay
2022-08-12 2:29 ` Haitao Huang
2022-08-12 3:23 ` Dhanraj, Vijay
2022-08-14 18:08 ` Jarkko Sakkinen
2022-08-15 16:16 ` Dhanraj, Vijay
2022-08-12 5:47 ` Haitao Huang
2022-08-14 18:11 ` Jarkko Sakkinen
2022-08-14 18:05 ` Jarkko Sakkinen
2022-08-15 4:58 ` Haitao Huang
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=YvD/DUGRBR2Tns88@kernel.org \
--to=jarkko@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=haitao.huang@intel.com \
--cc=linux-sgx@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=vijay.dhanraj@intel.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.