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

[Xen-devel] System Calls in x86_32

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] System Calls in x86_32
From: Ahmed Moneeb Azab <amazab@xxxxxxxx>
Date: Tue, 17 Jun 2008 18:56:53 -0400
Delivery-date: Tue, 17 Jun 2008 15:57:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (Windows/20080421)
Hi All,

I need help understanding how the direct system calls work on the x86_32 architecture.

What I understand is that when a guest is initialized, it uses the hypercall do_set_trap_table to initialize the trap table which calls init_int80_direct_trap for system call interrupts. The later updates the int80_desc structure in the VCPU of the guest so that the new address gets the callback directly.

What I do not understand is where does the call back occur. Int80 is not handles in the x86_32's entry.S?!!!! So, where is the code that issues the callback?

Why is architecture is different on x86_64. The entry.S contains an entry for int80. Does this affect the performance of the guests?

Ahmed


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

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