| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: Performance overhead of paravirt_ops on native identifie
|
To: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
|
Subject: |
[Xen-devel] Re: Performance overhead of paravirt_ops on native identified |
|
From: |
"H. Peter Anvin" <hpa@xxxxxxxxx> |
|
Date: |
Thu, 21 May 2009 16:10:06 -0700 |
|
Cc: |
Nick Piggin <npiggin@xxxxxxx>, "Xin, Xiaohui" <xiaohui.xin@xxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Chuck Ebbert <cebbert@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, "Li, Xin" <xin.li@xxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx> |
|
Delivery-date: |
Thu, 21 May 2009 16:11:17 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<4A15DA4E.2090505@xxxxxxxx> |
|
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: |
<4A0B62F7.5030802@xxxxxxxx> <20090521184233.3c3e97ad@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4A15DA4E.2090505@xxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Thunderbird 2.0.0.21 (X11/20090320) |
Jeremy Fitzhardinge wrote:
>
> In this specific instance of this example, yes. But if you start
> enabling various spinlock debug options then there'll be code following
> the call. It would be hard for the runtime patching machinery to know
> when it would be safe to do the substitution.
>
"When it is immediately followed by a ret" seems like a straightforward
rule to me?
-hpa
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Performance overhead of paravirt_ops on nativeidentified, (continued)
Re: [Xen-devel] Performance overhead of paravirt_ops on nativeidentified, Peter Zijlstra
[Xen-devel] [tip:x86/urgent] x86: Fix performance regression caused by paravirt_ops on native kernels, tip-bot for Jeremy Fitzhardinge
[Xen-devel] Re: Performance overhead of paravirt_ops on native identified, Chuck Ebbert
- [Xen-devel] Re: Performance overhead of paravirt_ops on native identified, Jeremy Fitzhardinge
- [Xen-devel] Re: Performance overhead of paravirt_ops on native identified,
H. Peter Anvin <=
- [Xen-devel] RE: Performance overhead of paravirt_ops on native identified, Xin, Xiaohui
- [Xen-devel] Re: Performance overhead of paravirt_ops on native identified, H. Peter Anvin
- [Xen-devel] Re: Performance overhead of paravirt_ops on native identified, Jeremy Fitzhardinge
- [Xen-devel] RE: Performance overhead of paravirt_ops on native identified, Xin, Xiaohui
- [Xen-devel] Re: Performance overhead of paravirt_ops on native identified, H. Peter Anvin
- [Xen-devel] Re: Performance overhead of paravirt_ops on native identified, Jeremy Fitzhardinge
- [Xen-devel] Re: Performance overhead of paravirt_ops on native identified, H. Peter Anvin
|
|
|
| |
|
Home