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/
Home Products Support Community News


Re: [Xen-devel] Different esps

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Different esps
From: Jacob Gorm Hansen <jacob@xxxxxxxx>
Date: Tue, 20 Jan 2004 19:29:03 +0100
Cc: Steven Hand <Steven.Hand@xxxxxxxxxxxx>, Xen list <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 20 Jan 2004 18:29:23 +0000
Envelope-to: Steven.Hand@xxxxxxxxxxxx
In-reply-to: <E1Aj0Ye-0007sm-00@xxxxxxxxxxxxxxxxxxxx>
References: <E1Aj0Ye-0007sm-00@xxxxxxxxxxxxxxxxxxxx>
On Tue, 2004-01-20 at 19:24, Keir Fraser wrote:

> >     HYPERVISOR_set_trap_table(trap_table);
> >     HYPERVISOR_set_fast_trap(SYSCALL_VECTOR);
> The alternative is to copy this info between the
> full_execution_context's of the old and new domains.

Except that with my setup I do not have access to these, unless there is
a way to map them from within each unprivileged domain.

> Looks weird. Why not instrument Xenolinux's trap handlers to see which
> exception you are occasionally taking. It's not hard -- most go thru
> do_trap() in arch/xeno/kernel/traps.c. GPFs and page faults go thru
> separate specialised functions.

It seems with a little more wiggling of things (especially installing
the trap vectors _before_ touching the ring1 stack of current) makes me
run quite a bit further, though not really far.


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