All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: linux-kernel@vger.kernel.org, mingo@kernel.org, x86@kernel.org,
	torvalds@linux-foundation.org
Cc: luto@kernel.org, ak@linux.intel.com, tglx@linutronix.de,
	dan.j.williams@intel.com
Subject: [PATCH 0/2] x86/entry: xorq->xorl; idtentry size reduction
Date: Wed, 14 Feb 2018 18:59:22 +0100	[thread overview]
Message-ID: <20180214175924.23065-1-linux@dominikbrodowski.net> (raw)

These two patches apply on top of tip/pti.

The first one cuts the idtentry macro as suggested by Linus.
I'm not sure whether this patch yet needs an explicit SOB by
him though. It was previously sent as RFC / testing only patch
"8/7" to the previous x86/entry-related series, cf.
http://lkml.kernel.org/r/20180211104949.12992-9-linux@dominikbrodowski.net

The other one replaces the xorq-based register cleaning with an
equivalent xorl-based version, which is supposed to be faster on
some architectures.

Thanks,
	Dominik

Dominik Brodowski (2):
  x86/entry: reduce static footprint of idtentry
  x86/entry/64: use xorl for register clearing

 arch/x86/entry/calling.h         | 27 +++++++++++++-------
 arch/x86/entry/entry_64.S        | 18 ++++++--------
 arch/x86/entry/entry_64_compat.S | 54 ++++++++++++++++++++--------------------
 3 files changed, 53 insertions(+), 46 deletions(-)

-- 
2.16.1

             reply	other threads:[~2018-02-14 18:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 17:59 Dominik Brodowski [this message]
2018-02-14 17:59 ` [PATCH 1/2] x86/entry: reduce static footprint of idtentry Dominik Brodowski
2018-02-17 11:40   ` [tip:x86/pti] x86/entry: Reduce the code footprint of the 'idtentry' macro tip-bot for Dominik Brodowski
2018-02-17 12:28     ` Dominik Brodowski
2018-02-14 17:59 ` [PATCH 2/2] x86/entry/64: use xorl for register clearing Dominik Brodowski
2018-02-17 11:40   ` [tip:x86/pti] x86/entry/64: Use 'xorl' for faster " tip-bot for Dominik Brodowski

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=20180214175924.23065-1-linux@dominikbrodowski.net \
    --to=linux@dominikbrodowski.net \
    --cc=ak@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.