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-devel

Re: [Xen-devel] Re: System Call Interception

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: System Call Interception
From: Adrian Chadd <adrian@xxxxxxxxxxxxxxx>
Date: Thu, 23 Nov 2006 23:52:43 +0800
Delivery-date: Thu, 23 Nov 2006 07:52:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4564ABC8.5090704@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20061119191018.6306.qmail@xxxxxxxxxxxxxxxxxxxxxxx> <4561DA1E.60108@xxxxxxxxxx> <4564ABC8.5090704@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
> >On i386 at least, syscalls are delivered directly to the guest (they 
> >aren't intercepted by Xen).

Also note that not all syscalls on all OSes are implemented the same
way - eg stuff like getpid()/gettimeofday()  might end up mapping to
some data hiding away in a page mapped to all processes. I'm not sure
Xen would even get involved in that (besides, perhaps, being involved
in page mapping?)

I forget which OSes I've seen do this by using dynamic linking magic;
solaris maybe?



Adrian


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

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