[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D2RQXM679U0X.1XY6BWHSFTRFZ@kernel.org>
Date: Wed, 17 Jul 2024 13:36:08 +0300
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Dmitrii Kuvaiskii" <dmitrii.kuvaiskii@...el.com>,
<dave.hansen@...ux.intel.com>, <kai.huang@...el.com>,
<haitao.huang@...ux.intel.com>, <reinette.chatre@...el.com>,
<linux-sgx@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Cc: <mona.vij@...el.com>, <kailun.qin@...el.com>, <stable@...r.kernel.org>
Subject: Re: [PATCH v4 1/3] x86/sgx: Split SGX_ENCL_PAGE_BEING_RECLAIMED
into two flags
On Fri Jul 5, 2024 at 10:45 AM EEST, Dmitrii Kuvaiskii wrote:
> SGX_ENCL_PAGE_BEING_RECLAIMED flag is set when the enclave page is being
> reclaimed (moved to the backing store). This flag however has two
> logical meanings:
~~~~~~~~
side-effects
Missing the actor.
"The page reclaimer thread sets SGX_ENC_PAGE_BEING_RECLAIMED flag..."
It is not just randomly "set".
>
> 1. Don't attempt to load the enclave page (the page is busy).
Please point out where in the source code.
> 2. Don't attempt to remove the PCMD page corresponding to this enclave
> page (the PCMD page is busy).
Please point out where in the source code.
These would be great reference when looking back.
>
> To reflect these two meanings, split SGX_ENCL_PAGE_BEING_RECLAIMED into
I don't care about meanings. Only who does and what.
BR, Jarkko
Powered by blists - more mailing lists