mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: luto@kernel.org, tglx@linutronix.de
Cc: keescook@chromium.org, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	Gabriel Krisman Bertazi <krisman@collabora.com>,
	kernel@collabora.com
Subject: [PATCH 0/6] Reclaim x86 psABI TIF flags
Date: Tue, 28 Jul 2020 16:22:23 -0400	[thread overview]
Message-ID: <20200728202229.1195682-1-krisman@collabora.com> (raw)

Hi,

This patch set reduces the number of arch-specific TIF_ flags in x86, as
a clean up to reduce the pressure over the few remaining x86_32 TIF
bits and as a preparation to have the arch-agnostic TIF_ flags shared by
different architectures by the common syscall entry code recently
published by Thomas Gleixner.

This is based on top of:

git://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git x86/entry

It was tested by booting and running an i386 rootfs over the 64bit
kernel, and also by running x32 binaries on top of it.

There is one remaining use of TIF_IA32 in User Mode Linux which is
turned off by a bogus define, such that I think it is currently dead
code and apparently a bug.  I think, it was wired to an old TIF_IA32
flag definition that doesn't exist anymore in arch/um.  I think it
deserves a fix other than dropping that code, but it is a different
piece of work that I will tackle next.

Gabriel Krisman Bertazi (6):
  arch: x86: Don't use TIF flags for mm context
  arch: x86: Wrap TIF_IA32 checks
  arch: x86: Wrap TIF_X32 checks
  arch: x86: Expose psABI on thread_info
  arch: x86: Reclaim TIF_IA32 flag
  arch: x86: Reclaim TIF_X32 flag

 arch/x86/entry/vdso/vma.c          |  2 +-
 arch/x86/events/core.c             |  4 ++--
 arch/x86/events/intel/ds.c         |  2 +-
 arch/x86/events/intel/lbr.c        |  2 +-
 arch/x86/include/asm/compat.h      |  2 +-
 arch/x86/include/asm/elf.h         |  2 +-
 arch/x86/include/asm/mmu_context.h |  2 +-
 arch/x86/include/asm/thread_info.h | 15 +++++++++++----
 arch/x86/kernel/perf_regs.c        |  2 +-
 arch/x86/kernel/process_64.c       | 16 ++++++----------
 arch/x86/oprofile/backtrace.c      |  2 +-
 11 files changed, 27 insertions(+), 24 deletions(-)

-- 
2.27.0


             reply	other threads:[~2020-07-28 20:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 20:22 Gabriel Krisman Bertazi [this message]
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
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=20200728202229.1195682-1-krisman@collabora.com \
    --to=krisman@collabora.com \
    --cc=keescook@chromium.org \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.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

Powered by JetHome