From: "Jan Beulich" <JBeulich@suse.com>
To: <mingo@elte.hu>, <tglx@linutronix.de>, <hpa@zytor.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] x86-64: allow using RIP-relative addressing for per-CPU data
Date: Tue, 04 Nov 2014 08:49:32 +0000 [thread overview]
Message-ID: <5458A12C0200007800044A97@mail.emea.novell.com> (raw)
Observing that per-CPU data (in the SMP case) is reachable by
exploiting 64-bit address wraparound, these two patches
arrange for using the one byte shorter RIP-relative addressing
forms for the majority of per-CPU accesses.
1: handle PC-relative relocations on per-CPU data
2: use RIP-relative addressing for most per-CPU accesses
Signed-off-by: Jan Beulich <jbeulich@suse.com>
next reply other threads:[~2014-11-04 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 8:49 Jan Beulich [this message]
2014-11-04 19:33 ` [PATCH 0/2] x86-64: allow using RIP-relative addressing for per-CPU data Andy Lutomirski
2014-11-05 17:09 ` Jan Beulich
2014-11-05 17:15 ` Andy Lutomirski
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=5458A12C0200007800044A97@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).