From: Dave Hansen <dave.hansen@intel.com>
To: Nataliia Bondarevska <bondarn@google.com>
Cc: "Reshetova, Elena" <elena.reshetova@intel.com>,
"Annapurve, Vishal" <vannapurve@google.com>,
"jarkko@kernel.org" <jarkko@kernel.org>,
"seanjc@google.com" <seanjc@google.com>,
"Huang, Kai" <kai.huang@intel.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Scarlata, Vincent R" <vincent.r.scarlata@intel.com>,
"Cai, Chong" <chongc@google.com>,
"Aktas, Erdem" <erdemaktas@google.com>,
"Raynor, Scott" <scott.raynor@intel.com>
Subject: Re: [PATCH v15 0/5] Enable automatic SVN updates for SGX enclaves
Date: Mon, 29 Sep 2025 13:50:16 -0700 [thread overview]
Message-ID: <1881634c-7a19-4570-b7de-54ce50e76675@intel.com> (raw)
In-Reply-To: <CAFbLv2fPwV6u8HX=zKntVLwKeBsbEu62J49uC0kL237HDRiUfQ@mail.gmail.com>
On 9/29/25 13:33, Nataliia Bondarevska wrote:
>> Could someone please spend a few minutes to explain what this tag means?
> My apologies; I've clarified the details of the testing below.
>
> The verification was performed on a SPR machine. The objective was to
> confirm the successful, runtime update of the CPUSVN using a targeted
> microcode package.
> Steps Taken:
> - identified a microcode package version, designed to update CPUSVN
> number on the machine;
> - initiated a dynamic load of the package during OS runtime;
> - confirmed the CPUSVN was upgraded post-load.
OK, so you're basically saying it managed to update the SVN on real
hardware. You also had to go run an enclave or at least open /dev/sgx,
right?
Also, does this tag mean, "I tested this in my company's environment and
this ABI is sufficient for us until the end of time?" Because there was
also some feedback on earlier work that this series as-is was going to
be insufficient.
next prev parent reply other threads:[~2025-09-29 20:50 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 ` [PATCH v15 0/5] " Dave Hansen
2025-09-05 21:18 ` 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 [this message]
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=1881634c-7a19-4570-b7de-54ce50e76675@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®