From: Jarkko Sakkinen <jarkko@kernel.org>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Shuah Khan <shuah@kernel.org>,
"open list:INTEL SGX" <linux-sgx@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] selftests/sgx: Use rip relative addressing for encl_stack
Date: Wed, 30 Mar 2022 23:40:56 +0300 [thread overview]
Message-ID: <d44b3fc7ce9f053f978645dfe19018885d372d87.camel@kernel.org> (raw)
In-Reply-To: <ef991f0d-d0d2-f422-96d8-0951d593d2a5@intel.com>
On Wed, 2022-03-30 at 13:05 -0700, Reinette Chatre wrote:
>
>
> On 3/30/2022 12:03 PM, Jarkko Sakkinen wrote:
> > On Wed, 2022-03-30 at 10:40 -0700, Reinette Chatre wrote:
> > > Could you please elaborate how the compiler will fix it up?
> >
> > Sure.
> >
> > Here's the disassembly of the RBX version:
> >
> > [0x000021a9]> pi 1
> > lea rax, [rbx + loc.encl_stack]
> >
> > Here's the same with s/RBX/RIP/:
> >
> > [0x000021a9]> pi 5
> > lea rax, loc.encl_stack
> >
> > Compiler will substitute correct offset relative to the RIP,
> > well, because it can and it makes sense.
>
> It does not make sense to me because, as proven with my test,
> the two threads end up sharing the same stack memory.
I see, I need to correct my patch, thanks!
RBX gives correct results because of the binary organization,
i.e. TCS's are placed to zero offset and forward, and
unrelocated symbol is just compiled in as an untranslated
offset.
RPI is given correct results but how the semantics work
right now is incompatible.
Still, even for kselftest, I would consider a switch
because that way:
1. You can layout binary however you wan and things
won't break.
2. You can point to any symbol not just stack, if
ever need.
I admit it works semantically but it just super
unrobust.
BR, Jarkko
next prev parent reply other threads:[~2022-03-30 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 7:43 [PATCH v2 1/2] selftests/sgx: Use rip relative addressing for encl_stack Jarkko Sakkinen
2022-03-22 7:43 ` [PATCH v2 2/2] selftests/sgx: Make TCS table relocatable Jarkko Sakkinen
2022-03-28 21:49 ` [PATCH v2 1/2] selftests/sgx: Use rip relative addressing for encl_stack Reinette Chatre
2022-03-30 14:54 ` Jarkko Sakkinen
2022-03-30 14:56 ` Jarkko Sakkinen
2022-03-30 17:40 ` Reinette Chatre
[not found] ` <f68d472877b7136c32d8770603a3de38de59c322.camel@kernel.org>
2022-03-30 19:22 ` Jarkko Sakkinen
2022-03-30 20:05 ` Reinette Chatre
2022-03-30 20:40 ` Jarkko Sakkinen [this message]
2022-03-30 21:29 ` Reinette Chatre
2022-03-30 22:30 ` Jarkko Sakkinen
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=d44b3fc7ce9f053f978645dfe19018885d372d87.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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