From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Christoph Hellwig <hch@lst.de>,
Thomas Gleixner <tglx@linutronix.de>,
Kees Cook <keescook@chromium.org>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel@collabora.com
Subject: Re: [PATCH 2/6] arch: x86: Wrap TIF_IA32 checks
Date: Wed, 29 Jul 2020 14:11:44 -0400 [thread overview]
Message-ID: <874kpqjin3.fsf@collabora.com> (raw)
In-Reply-To: <CALCETrUVQw4EUyEFQ4xdWBrxVKJtNmrZurGccXtn8i9nNAYufg@mail.gmail.com> (Andy Lutomirski's message of "Tue, 28 Jul 2020 22:09:26 -0700")
Andy Lutomirski <luto@kernel.org> writes:
> On Tue, Jul 28, 2020 at 9:46 PM Gabriel Krisman Bertazi
> <krisman@collabora.com> wrote:
>>
>> Andy Lutomirski <luto@kernel.org> writes:
>>
>> > On Tue, Jul 28, 2020 at 1:22 PM Gabriel Krisman Bertazi
>> > <krisman@collabora.com> wrote:
>> >>
>> >> In preparation to remove TIF_IA32, add wrapper that check the process
>> >> has IA32 ABI without using the flag directly.
>> >
>> > Thank you for doing this, but let's please do it right. There is,
>> > fundamentally, no such thing as a "process with IA32 ABI".
>>
>> Hi Andy,
>>
>> Thanks a lot for your review.
>>
>> As you can see, I'm learning my way here. Can you clarify "there is no
>> such a thing as a 'process with IA32 ABI'"? I'm not sure if I confused
>> the terminology or if (more worrisome for me) I got the concepts wrong.
>>
>> My understanding is that TIF_IA32 marks a thread that is running under
>> the 32-bit compat mode, which would be running a 32-bit process (as in
>> compiled with -m32, for instance), while TIF_X32 marks a process running
>> under the X32 ABI. Each process would have only one of these
>> "personalities". This is what I meant by a process with IA32 ABI (which
>> is wrong in any case). Is there more to it, or is the problem the
>> terminology I used?
>
> There's more to it.
Thanks again for the explanation!
>> I don't have any comments on the other things you mentioned, except that
>> I need to go through them and better understand your suggestions. Would
>> you prefer me to rework this patch series with what you suggested or is
>> this something you want to take over and do yourself? Both ways are
>> fine by me.
>
> Please rework it :) I have seriously limited bandwidth right now.
Will do.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2020-07-29 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 20:22 [PATCH 0/6] Reclaim x86 psABI TIF flags Gabriel Krisman Bertazi
2020-07-28 20:22 ` [PATCH 1/6] arch: x86: Don't use TIF flags for mm context Gabriel Krisman Bertazi
2020-07-29 9:03 ` peterz
2020-07-28 20:22 ` [PATCH 2/6] arch: x86: Wrap TIF_IA32 checks Gabriel Krisman Bertazi
2020-07-29 3:43 ` Andy Lutomirski
2020-07-29 4:46 ` Gabriel Krisman Bertazi
2020-07-29 5:09 ` Andy Lutomirski
2020-07-29 18:11 ` Gabriel Krisman Bertazi [this message]
2020-07-29 6:59 ` Christoph Hellwig
2020-07-29 9:11 ` peterz
2020-07-28 20:22 ` [PATCH 3/6] arch: x86: Wrap TIF_X32 checks Gabriel Krisman Bertazi
2020-07-29 4:54 ` Andy Lutomirski
2020-07-28 20:22 ` [PATCH 4/6] arch: x86: Expose psABI on thread_info Gabriel Krisman Bertazi
2020-07-29 3:44 ` Andy Lutomirski
2020-07-28 20:22 ` [PATCH 5/6] arch: x86: Reclaim TIF_IA32 flag Gabriel Krisman Bertazi
2020-07-28 20:22 ` [PATCH 6/6] arch: x86: Reclaim TIF_X32 flag Gabriel Krisman Bertazi
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=874kpqjin3.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=hch@lst.de \
--cc=keescook@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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