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

[Xen-users] Where do System calls go?


  • To: xen list <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: helicoterus-elih@xxxxxxxx
  • Date: Thu, 30 Apr 2009 14:48:00 +0000 (GMT)
  • Delivery-date: Thu, 30 Apr 2009 09:32:45 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.it; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=nGNThToeFBHh2sh1o8bIOxjTvKYLddyET6hC2xpIb7uAtNMGmdxcNMrwQXcmH64b+X+6jcXA4dJCiySY8Al5wLZtF3z6fN8E75/G0EZ9z4Knbev4ixM2jjBmX2OycZa8SUyrOBLHibJO+YNiHOga2649I9L6zaIFcGob3cMmNJM=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I have a doubt about system calls on paravirtualized Xen environment (without 
virtualization extensions).
When a program on a domU invokes a sys call, this arrives to its kernel (on 
ring 3) and then it is send to VMM (on ring 0) or system call goes directly to 
VMM?
Normally a system call goes to its O.S. libc and then a handler on kernel 
carries it on.
I do not understand what is the problem of sys call.

Thank you.





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


 


Rackspace

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