[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4978F6C6.3090003@goop.org>
Date: Thu, 22 Jan 2009 14:44:22 -0800
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Zachary Amsden <zach@...are.com>
CC: Jeremy Fitzhardinge <jeremy@...p.org>,
Nick Piggin <npiggin@...e.de>, Ingo Molnar <mingo@...e.hu>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"hpa@...or.com" <hpa@...or.com>,
"jeremy@...source.com" <jeremy@...source.com>,
"chrisw@...s-sol.org" <chrisw@...s-sol.org>,
"rusty@...tcorp.com.au" <rusty@...tcorp.com.au>,
Andrew Morton <akpm@...ux-foundation.org>,
Xen-devel <xen-devel@...ts.xensource.com>
Subject: Re: lmbench lat_mmap slowdown with CONFIG_PARAVIRT
Zachary Amsden wrote:
> These fragments, from native_pgd_val, certainly don't help:
>
> c0120f60: 55 push %ebp
> c0120f61: 89 e5 mov %esp,%ebp
> c0120f63: 5d pop %ebp
> c0120f64: c3 ret
> c0120f65: 8d 74 26 00 lea 0x0(%esi,%eiz,1),%esi
> c0120f69: 8d bc 27 00 00 00 00 lea 0x0(%edi,%eiz,1),%edi
>
Yes, that's a rather awful noop; compiling without frame pointers
reduces this to a single "ret".
> That is really disgusting. We absolutely should be patching away the
> function calls here in the native case.. not sure we do that today.
>
I did have some patches to do that at one point. If you set pgd_val =
paravirt_nop, then the patching machinery will completely nop out the
call site. The problem is that it depends on the calling convention
using the same regs for the first arg and return - true for 32-bit, but
not 64. We could fix that with identity functions which the patcher
recognizes and can replace with either pure nops or inline appropriate
register moves.
Also, I just posted patches to get rid of all pvops calls when fetching
or setting flags in a pte, which I hope will help.
J
--
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