[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Re: [patch 13/26] Xen-paravirt_ops: Consistently wrap paravirt ops callsites to make them patchable
- To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
- From: Andi Kleen <ak@xxxxxx>
- Date: 18 Mar 2007 18:04:14 +0100
- Date: Sun, 18 Mar 2007 18:04:14 +0100
- Cc: zach@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, rusty@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, chrisw@xxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxx, anthony@xxxxxxxxxxxxx, mingo@xxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, David Miller <davem@xxxxxxxxxxxxx>
- Delivery-date: Sun, 18 Mar 2007 10:03:13 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
> The bigger problem is that you don't know what registers you can
> clobber. For the pv_ops in hand-written asm, that a big pain. The code
> either has to assume the worst, or the "relocator" has to do something
> more sophisticated (like look for push/pop pairs surrounding the call,
> perhaps?).
You could use the dwarf2 unwind tables. They have exact information
what register has what. But it would likely get complicated.
-Andi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
