[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel][PATCH] optimize entry and exit path


  • To: <ahs3@xxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Tue, 11 Jul 2006 09:47:43 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 10 Jul 2006 18:48:02 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcakZPMnvvOePQZyR8KXe94hNWrHawAJnkQg
  • Thread-topic: [Xen-ia64-devel][PATCH] optimize entry and exit path

>From: Al Stone [mailto:ahs3@xxxxxxxxx]
>Sent: 2006?7?11? 5:07
>If I understand this patch correctly, and I'm not sure I do, so please
>bear with me, it looks like I now have two entry points into the same
>block of code -- GLOBAL_ENTRY(ia64_leave_hypervisor_prepare) and a few
>instructions later, GLOBAL_ENTRY(ia64_leave_hypervisor).  That makes
>sense if the goal is to shave off some instructions that are not always
>necessary.  I've used that trick many times myself.
>
Totally correct,
>What puzzles me, though, is what happens to the unwind info?  Without
>an END for ia64_leave_hypervisor_prepare, am I losing unwind info, or
>possibly confusing the info for ia64_leave_hypervisor?  Or am I just
>not seeing something obvious?
>
Good point,
To be honest, I didn't think of unwind info,
>I'm still trying to grok Xen, so be gentle :)...
>
>--
>Ciao,
>al
>----------------------------------------------------------------------
>Al Stone                                      Alter Ego:
>Open Source and Linux R&D                     Debian Developer
>Hewlett-Packard Company                       http://www.debian.org
>E-mail: ahs3@xxxxxxxxx                        ahs3@xxxxxxxxxx
>----------------------------------------------------------------------

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.