| 
         
xen-devel
[Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been
 
| 
To:  | 
Richard Henderson <rth@xxxxxxxxxx> | 
 
| 
Subject:  | 
[Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out | 
 
| 
From:  | 
Steven Rostedt <rostedt@xxxxxxxxxxx> | 
 
| 
Date:  | 
Thu, 06 Oct 2011 15:28:39 -0400 | 
 
| 
Cc:  | 
Jeremy Fitzhardinge <jeremy@xxxxxxxx>,	arch/x86 maintainers <x86@xxxxxxxxxx>,	Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>,	David Daney <david.daney@xxxxxxxxxx>, peterz@xxxxxxxxxxxxx,	Jason Baron <jbaron@xxxxxxxxxx>, Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>,	Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>,	Michael Ellerman <michael@xxxxxxxxxxxxxx>,	Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>,	"H. Peter Anvin" <hpa@xxxxxxxxx>, the,	"David S. Miller" <davem@xxxxxxxxxxxxx> | 
 
| 
Delivery-date:  | 
Thu, 06 Oct 2011 12:31:13 -0700 | 
 
| 
Envelope-to:  | 
www-data@xxxxxxxxxxxxxxxxxxx | 
 
| 
In-reply-to:  | 
<4E8DF870.6010000@xxxxxxxxxx> | 
 
| 
List-help:  | 
<mailto:xen-devel-request@lists.xensource.com?subject=help> | 
 
| 
List-id:  | 
Xen developer discussion <xen-devel.lists.xensource.com> | 
 
| 
List-post:  | 
<mailto:xen-devel@lists.xensource.com> | 
 
| 
List-subscribe:  | 
<http://lists.xensource.com/mailman/listinfo/xen-devel>,	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe> | 
 
| 
List-unsubscribe:  | 
<http://lists.xensource.com/mailman/listinfo/xen-devel>,	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> | 
 
| 
References:  | 
<cover.1317506051.git.jeremy.fitzhardinge@xxxxxxxxxx>	<477dead9647029012f93c651f2892ed0e86b89e7.1317506051.git.jeremy.fitzhardinge@xxxxxxxxxx>	<20111003150205.GB2462@xxxxxxxxxx> <4E89E28C.7010700@xxxxxxxx>	<20111004141011.GA2520@xxxxxxxxxx> <4E8B3489.60902@xxxxxxxxx>	<4E8CF348.4080405@xxxxxxxx> <4E8CF385.2080804@xxxxxxxxx>	<4E8DEB19.1050509@xxxxxxxx> <20111006181055.GA2505@xxxxxxxxxx>	<1317925615.4729.14.camel@xxxxxxxxxxxxxxxxxxx>	<4E8DF870.6010000@xxxxxxxxxx> | 
 
| 
Sender:  | 
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx | 
 
 
 
On Thu, 2011-10-06 at 11:50 -0700, Richard Henderson wrote:
> On 10/06/2011 11:26 AM, Steven Rostedt wrote:
>  
> > 
> > That jmp to l_yes should easily be a two byte jump.
> 
> Until the compiler decides to re-order the code.  That's the problem --
> in the general case you do not know how far away the destination is really
> going to be.
Yeah, I was discussing this with Peter Zijlstra on IRC.
> 
> There are a couple of possibilities for improvement:
> 
> (1) Do as Jason suggests above and let the assembler figure out the size
> of the branch that is needed.  Without adding more data to __jump_table,
> you'll want to be extremely careful about checking the two pointers to 
> see what size branch has been installed.
Yeah, that could be done at patch time.
> 
> (2) Always reserve 5 bytes of space, but if the distance is small enough
> patch in a 2-byte jump.  That doesn't help with the icache footprint.
I don't think this one is worth it.
-- Steve
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 |   
 
| <Prev in Thread] | 
Current Thread | 
[Next in Thread>
 |  
- [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, (continued)
 
- [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, Steven Rostedt
 - [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, H. Peter Anvin
 - [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, Jason Baron
 - [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, Steven Rostedt
 - [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, Jason Baron
 - [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, Steven Rostedt
 
- [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, Richard Henderson
 - [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out,
Steven Rostedt <=
 - [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, Jeremy Fitzhardinge
 - [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, Steven Rostedt
 - [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, Jeremy Fitzhardinge
 - [Xen-devel] Re: [PATCH RFC V2 3/5] jump_label: if a key has already been initialized, don't nop it out, Steven Rostedt
 
- [Xen-devel] [PATCH][RFC] jump_labels/x86: Use either 5 byte or 2	byte jumps, Steven Rostedt
 - [Xen-devel] Re: [PATCH][RFC] jump_labels/x86: Use either 5 byte or	2 byte jumps, Jeremy Fitzhardinge
 - [Xen-devel] Re: [PATCH][RFC] jump_labels/x86: Use either 5 byte or	2 byte jumps, Peter Zijlstra
 
- [Xen-devel] Re: [PATCH][RFC] jump_labels/x86: Use either 5 byte or	2 byte jumps, Steven Rostedt
 
- [Xen-devel] Re: [PATCH][RFC] jump_labels/x86: Use either 5 byte or	2 byte jumps, Jason Baron
 - [Xen-devel] Re: [PATCH][RFC] jump_labels/x86: Use either 5 byte or	2 byte jumps, Steven Rostedt
 
 
 |  
  
 | 
    |