From: Jo Van Bulck <jo.vanbulck@cs.kuleuven.be>
To: Jarkko Sakkinen <jarkko@kernel.org>,
linux-sgx@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: dave.hansen@linux.intel.com
Subject: Re: [PATCH 2/4] selftests/sgx: Store base address and size in test enclave
Date: Thu, 20 Jul 2023 21:18:41 +0200 [thread overview]
Message-ID: <818446ff-082f-7bef-eded-9fb14524db13@cs.kuleuven.be> (raw)
In-Reply-To: <CU76ENNUAMHF.15D3KJY99C50@suppilovahvero>
On 20.07.23 19:29, Jarkko Sakkinen wrote:
>> diff --git a/tools/testing/selftests/sgx/main.c b/tools/testing/selftests/sgx/main.c
>> index d3c7a39f4..bad963c79 100644
>> --- a/tools/testing/selftests/sgx/main.c
>> +++ b/tools/testing/selftests/sgx/main.c
>> @@ -182,6 +1827 @@ static bool setup_test_encl(unsigned long heap_size, struct encl *encl,
>> FILE *maps_file;
>> unsigned int i;
>> void *addr;
>> + uint64_t encl_size_addr;
>
> Should be the first declaration (reverse xmas tree order).
Will do
> I'd rename this as encl_end, as the current name is cryptic.
Thank you, agreed the current name is cryptic. However, encl_end is
incorrect as this is the location in the enclave that stores the _size_
and the location itself is also _not_ at the end of the enclave.
I'll rename this in the next patch revision to encl_size_pt and make it
of type uint64_t*, which seems more logical to me. Let me know if you
prefer otherwise!
Best,
Jo
next prev parent reply other threads:[~2023-07-20 19:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 14:24 [PATCH 0/4] selftests/sgx: Harden test enclave Jo Van Bulck
2023-07-19 14:24 ` [PATCH 1/4] selftests/sgx: Harden test enclave ABI Jo Van Bulck
2023-07-20 17:27 ` Jarkko Sakkinen
2023-07-20 19:14 ` Jo Van Bulck
2023-07-19 14:24 ` [PATCH 2/4] selftests/sgx: Store base address and size in test enclave Jo Van Bulck
2023-07-20 17:29 ` Jarkko Sakkinen
2023-07-20 19:18 ` Jo Van Bulck [this message]
2023-07-19 14:24 ` [PATCH 3/4] selftests/sgx: Harden test enclave API Jo Van Bulck
2023-07-20 17:32 ` Jarkko Sakkinen
2023-07-20 19:34 ` Jo Van Bulck
2023-07-19 14:25 ` [PATCH 4/4] selftests/sgx: Fix compiler optimizations in test enclave Jo Van Bulck
2023-07-20 17:25 ` [PATCH 0/4] selftests/sgx: Harden " Jarkko Sakkinen
2023-07-20 19:12 ` Jo Van Bulck
2023-07-20 19:56 ` Dave Hansen
2023-07-20 20:57 ` Jo Van Bulck
2023-07-22 18:10 ` Jarkko Sakkinen
2023-07-24 10:46 ` Jo Van Bulck
2023-07-28 18:54 ` Jarkko Sakkinen
2023-08-07 6:06 ` Jo Van Bulck
2023-08-07 11:58 ` Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
2023-07-20 22:16 [PATCH v2 " Jo Van Bulck
2023-07-20 22:16 ` [PATCH 2/4] selftests/sgx: Store base address and size in " Jo Van Bulck
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=818446ff-082f-7bef-eded-9fb14524db13@cs.kuleuven.be \
--to=jo.vanbulck@cs.kuleuven.be \
--cc=dave.hansen@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.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