From: Zhiquan Li <zhiquan1.li@intel.com>
To: linux-sgx@vger.kernel.org, tony.luck@intel.com
Cc: jarkko@kernel.org, dave.hansen@linux.intel.com,
seanjc@google.com, fan.du@intel.com, zhiquan1.li@intel.com
Subject: [PATCH 1/4] x86/sgx: Move struct sgx_vepc definition to sgx.h
Date: Tue, 10 May 2022 11:17:25 +0800 [thread overview]
Message-ID: <20220510031725.3181361-1-zhiquan1.li@intel.com> (raw)
Move struct sgx_vepc definition to sgx.h so that it can be used outside
of virt.c.
Signed-off-by: Zhiquan Li <zhiquan1.li@intel.com>
---
arch/x86/kernel/cpu/sgx/sgx.h | 5 +++++
arch/x86/kernel/cpu/sgx/virt.c | 5 -----
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/arch/x86/kernel/cpu/sgx/sgx.h b/arch/x86/kernel/cpu/sgx/sgx.h
index 0f17def9fe6f..83ff8c3e81cf 100644
--- a/arch/x86/kernel/cpu/sgx/sgx.h
+++ b/arch/x86/kernel/cpu/sgx/sgx.h
@@ -101,4 +101,9 @@ static inline int __init sgx_vepc_init(void)
void sgx_update_lepubkeyhash(u64 *lepubkeyhash);
+struct sgx_vepc {
+ struct xarray page_array;
+ struct mutex lock;
+};
+
#endif /* _X86_SGX_H */
diff --git a/arch/x86/kernel/cpu/sgx/virt.c b/arch/x86/kernel/cpu/sgx/virt.c
index 6a77a14eee38..c9c8638b5dc4 100644
--- a/arch/x86/kernel/cpu/sgx/virt.c
+++ b/arch/x86/kernel/cpu/sgx/virt.c
@@ -18,11 +18,6 @@
#include "encls.h"
#include "sgx.h"
-struct sgx_vepc {
- struct xarray page_array;
- struct mutex lock;
-};
-
/*
* Temporary SECS pages that cannot be EREMOVE'd due to having child in other
* virtual EPC instances, and the lock to protect it.
--
2.25.1
next reply other threads:[~2022-05-10 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 3:17 Zhiquan Li [this message]
2022-05-11 10:31 ` [PATCH 1/4] x86/sgx: Move struct sgx_vepc definition to sgx.h Jarkko Sakkinen
2022-05-12 12:10 ` Zhiquan Li
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=20220510031725.3181361-1-zhiquan1.li@intel.com \
--to=zhiquan1.li@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fan.du@intel.com \
--cc=jarkko@kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=seanjc@google.com \
--cc=tony.luck@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).