[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A15DF4E.6060209@zytor.com>
Date: Thu, 21 May 2009 16:10:06 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Jeremy Fitzhardinge <jeremy@...p.org>
CC: Chuck Ebbert <cebbert@...hat.com>, Ingo Molnar <mingo@...e.hu>,
"Xin, Xiaohui" <xiaohui.xin@...el.com>,
"Li, Xin" <xin.li@...el.com>,
"Nakajima, Jun" <jun.nakajima@...el.com>,
Nick Piggin <npiggin@...e.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Xen-devel <xen-devel@...ts.xensource.com>
Subject: Re: Performance overhead of paravirt_ops on native identified
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists