From: Dave Hansen <dave.hansen@intel.com>
To: Elena Reshetova <elena.reshetova@intel.com>
Cc: jarkko@kernel.org, seanjc@google.com, kai.huang@intel.com,
mingo@kernel.org, linux-sgx@vger.kernel.org,
linux-kernel@vger.kernel.org, x86@kernel.org,
asit.k.mallick@intel.com, vincent.r.scarlata@intel.com,
chongc@google.com, erdemaktas@google.com, vannapurve@google.com,
bondarn@google.com, scott.raynor@intel.com
Subject: Re: [PATCH v15 0/5] Enable automatic SVN updates for SGX enclaves
Date: Fri, 5 Sep 2025 12:37:18 -0700 [thread overview]
Message-ID: <287a2652-bce6-4084-b9b5-c8feb24a2940@intel.com> (raw)
In-Reply-To: <20250818071304.1717183-1-elena.reshetova@intel.com>
On 8/18/25 00:11, Elena Reshetova wrote:
> Testing
> -------
>
> Tested on EMR machine using kernel 6.17.0_rc1 & sgx selftests.
> Also tested on a Kaby Lake machine without EUPDATESVN support.
> If Google folks in CC can test on their side, it would be greatly
> appreciated.
Yeah, lots of @google.com addresses on Cc, but there's a dearth of tags
from those addresses.
next prev parent reply other threads:[~2025-09-05 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 7:11 Elena Reshetova
2025-08-18 7:11 ` [PATCH v15 1/5] x86/sgx: Introduce functions to count the sgx_(vepc_)open() Elena Reshetova
2025-08-18 7:11 ` [PATCH v15 2/5] x86/cpufeatures: Add X86_FEATURE_SGX_EUPDATESVN feature flag Elena Reshetova
2025-08-18 7:11 ` [PATCH v15 3/5] x86/sgx: Define error codes for use by ENCLS[EUPDATESVN] Elena Reshetova
2025-08-18 7:11 ` [PATCH v15 4/5] x86/sgx: Implement ENCLS[EUPDATESVN] Elena Reshetova
2025-08-18 7:11 ` [PATCH v15 5/5] x86/sgx: Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-09-05 19:37 ` Dave Hansen [this message]
2025-09-05 21:18 ` [PATCH v15 0/5] " Vishal Annapurve
2025-09-29 7:17 ` Reshetova, Elena
2025-09-29 17:12 ` Nataliia Bondarevska
2025-09-29 17:35 ` Dave Hansen
2025-09-29 20:33 ` Nataliia Bondarevska
2025-09-29 20:50 ` Dave Hansen
2025-09-29 21:58 ` Nataliia Bondarevska
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=287a2652-bce6-4084-b9b5-c8feb24a2940@intel.com \
--to=dave.hansen@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=bondarn@google.com \
--cc=chongc@google.com \
--cc=elena.reshetova@intel.com \
--cc=erdemaktas@google.com \
--cc=jarkko@kernel.org \
--cc=kai.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=scott.raynor@intel.com \
--cc=seanjc@google.com \
--cc=vannapurve@google.com \
--cc=vincent.r.scarlata@intel.com \
--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
all inboxes | Powered by JetHome®