WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

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

To: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
Subject: Re: [Xen-ia64-devel][PATCH] optimize entry and exit path
From: Al Stone <ahs3@xxxxxxxxx>
Date: Mon, 10 Jul 2006 15:07:19 -0600
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 10 Jul 2006 14:07:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <01913ADC4FF97E40AE0E2B001574AEE11F32F4@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Hewlett-Packard
References: <01913ADC4FF97E40AE0E2B001574AEE11F32F4@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: ahs3@xxxxxxxxx
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2006-07-10 at 15:24 +0800, Xu, Anthony wrote:
> VMM save/restore r4~r7 and unat to handle virtualization fault and mmio 
> access,
> but it is not necessary for other faults to save/restore these registers.
> This patch is to save/restore these registers only when dtlb and 
> virtualization fault happen.

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.

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?

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

<Prev in Thread] Current Thread [Next in Thread>