From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@muc.de>, Chuck Ebbert <cebbert@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [patch 5/8] Immediate Values - x86 Optimization (update 2)
Date: Wed, 14 Nov 2007 09:16:35 -0500 [thread overview]
Message-ID: <20071114141635.GB22251@Krystal> (raw)
In-Reply-To: <473A6471.4040700@zytor.com>
* H. Peter Anvin (hpa@zytor.com) wrote:
> Mathieu Desnoyers wrote:
>> Immediate Values - x86 Optimization
>> x86 optimization of the immediate values which uses a movl with code
>> patching
>> to set/unset the value used to populate the register used as variable
>> source.
>> Changelog:
>> - Use text_poke_early with cr0 WP save/restore to patch the bypass. We are
>> doing
>> non atomic writes to a code region only touched by us (nobody can
>> execute it
>> since we are protected by the immediate_mutex).
>> - Put immediate_set and _immediate_set in the architecture independent
>> header.
>> - Use $0 instead of %2 with (0) operand.
>> - Add x86_64 support, ready for i386+x86_64 -> x86 merge.
>> - Use asm-x86/asm.h.
>> Ok, so the most flexible solution that I see, that should fit for both
>> i386 and x86_64 would be :
>> 1 byte : "=Q" : Any register accessible as rh: a, b, c, and d.
>> 2, 4 bytes : "=R" : Legacy register—the eight integer registers
>> available
>> on all i386 processors (a, b, c, d, si, di, bp, sp). 8
>> bytes : (only for x86_64)
>> "=r" : A register operand is allowed provided that it is in a
>> general register.
>> That should make sure x86_64 won't try to use REX prefixed opcodes for
>> 1, 2 and 4 bytes values.
>
> I just had a couple of utterly sick ideas.
>
> Consider this variant (this example is for a 32-bit immediate on x86-64,
> but the obvious macroizations apply):
>
> .section __discard,"a",@progbits
> 1: movl $0x12345678,%r9d
> 2:
> .previous
>
> .section __immediate,"a",@progbits
> .quad foo_immediate, (3f)-4, 4
> .previous
>
> .org . + ((-.-(2b-1b)) & 3), 0x90
> movl $0x12345678,%r9d
> 3:
>
>
> The idea is that the instruction is emitted into a section, which is marked
> DISCARD in the linker script. That lets us actually measure the length,
> and since we know the immediate is always at the end of the instruction...
> done!
>
Wow! I like this idea. I'll give it a try in a test sandbox to see if
gas or ld complains. I'll keep you posted.
Mathieu
>
> -hpa
>
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2007-11-14 14:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 18:58 [patch 0/8] Immediate Values (now with merged x86 support) Mathieu Desnoyers
2007-11-13 18:58 ` [patch 1/8] Immediate Values - Architecture Independent Code Mathieu Desnoyers
2007-11-13 18:58 ` [patch 2/8] Immediate Values - Kconfig menu in EMBEDDED Mathieu Desnoyers
2007-11-13 18:58 ` [patch 3/8] Immediate Values - Move Kprobes x86 restore_interrupt to kdebug.h Mathieu Desnoyers
2007-11-13 18:58 ` [patch 4/8] Add asm-compat.h to x86 Mathieu Desnoyers
2007-11-13 19:05 ` H. Peter Anvin
2007-11-13 20:37 ` [patch 4/8] Add asm-compat.h to x86 -> use new asm.h instead Mathieu Desnoyers
2007-11-13 18:58 ` [patch 5/8] Immediate Values - x86 Optimization Mathieu Desnoyers
2007-11-13 19:07 ` H. Peter Anvin
2007-11-13 19:24 ` Mathieu Desnoyers
2007-11-13 19:36 ` H. Peter Anvin
2007-11-13 19:45 ` Mathieu Desnoyers
2007-11-13 19:56 ` H. Peter Anvin
2007-11-13 20:40 ` [patch 5/8] Immediate Values - x86 Optimization (update) Mathieu Desnoyers
2007-11-13 21:26 ` H. Peter Anvin
2007-11-13 22:02 ` Mathieu Desnoyers
2007-11-13 22:35 ` H. Peter Anvin
2007-11-14 0:34 ` Mathieu Desnoyers
2007-11-14 1:02 ` H. Peter Anvin
2007-11-14 1:44 ` [patch 5/8] Immediate Values - x86 Optimization (update 2) Mathieu Desnoyers
2007-11-14 2:58 ` H. Peter Anvin
2007-11-14 14:16 ` Mathieu Desnoyers [this message]
2007-11-14 18:52 ` [PATCH] Immediate Values x86 Optimization Declare Discarded Instruction Mathieu Desnoyers
2007-11-14 19:00 ` H. Peter Anvin
2007-11-14 19:16 ` [PATCH] Add __discard section to x86 Mathieu Desnoyers
2007-11-14 19:33 ` H. Peter Anvin
2007-11-15 3:08 ` [patch 5/8] Immediate Values - x86 Optimization Rusty Russell
2007-11-15 4:06 ` Mathieu Desnoyers
2007-11-15 4:45 ` Rusty Russell
2007-11-15 5:37 ` Mathieu Desnoyers
2007-11-15 11:06 ` Rusty Russell
2007-11-16 14:03 ` [patch 5/8] Immediate Values - x86 Optimization (simplified) Mathieu Desnoyers
2007-11-18 23:11 ` Rusty Russell
2007-11-19 14:28 ` Mathieu Desnoyers
2007-11-19 23:06 ` Rusty Russell
2007-11-20 17:02 ` Mathieu Desnoyers
2007-11-19 19:15 ` Mathieu Desnoyers
2007-11-13 18:58 ` [patch 6/8] Immediate Values - Powerpc Optimization Mathieu Desnoyers
2007-11-13 18:58 ` [patch 7/8] Immediate Values - Documentation Mathieu Desnoyers
2007-11-13 18:58 ` [patch 8/8] Scheduler Profiling - Use Immediate Values Mathieu Desnoyers
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=20071114141635.GB22251@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=cebbert@redhat.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.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