 Home |
Products |
Support |
Community |
News |
xen-users
[Xen-users] A question about SYSENTER/SYSEXIT in HVM guest
| To: | Xen-users@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-users] A question about SYSENTER/SYSEXIT in HVM guest |
| From: | Guofu Xiang <whxgf1984@xxxxxxxxx> |
| Date: | Mon, 6 Apr 2009 21:07:34 +0800 |
| Cc: | |
| Delivery-date: | Mon, 06 Apr 2009 06:08:14 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=+qyunDTQSpktOkscbHfHJLUKY9UXqWgsEGOyNn27IDM=; b=uQmjsKzPfof6VQPZRf/OFHQ8sS6i2j75f27g69EjZ+gqTPU0Ciiw2F+Yyk8h+mEubN R3iOE9Sl9IoiMucsRg5hurj1aJFaDc0+YEcFKRw424r5uct6u+hCMnFNdRd4Jas/NtqI d6BjGGyuitKrXjfGtj/e76chLfhmfNgB4i1xI= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=vyFhLfiOyQZMB4NqQcrw6dW8jE6TnkQ93S+sF5EZR8437R29GUj/dd4JzBGa7SkT3q lzjTrE2HWskdUeYSXnOL0NRh0gZzH7xjSy88EhGwIA07+r9+sys108S610zwWAI/tEAL M48lNKhxnbng7to1xNFgp5Bi0Jve3kNZuUNm8= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-users-request@lists.xensource.com?subject=help> |
| List-id: | Xen user discussion <xen-users.lists.xensource.com> |
| List-post: | <mailto:xen-users@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-users-bounces@xxxxxxxxxxxxxxxxxxx |
|
The CPU type of our server is Intel Xeon E5310, and the OS is Fedora 8. Xen 3.2 is installed by Compilation. When the HVM guest is x86_32 Fedora 8, the system call is implemented by instruction - int $80h. Our debug result by gdb is as follow.
Dump of assembler code for function __kernel_vsyscall:
0xb7f87400 <__kernel_vsyscall+0>: int $0x80 0xb7f87402 <__kernel_vsyscall+2>: ret End of assembler dump. However, when the HVM guest is x86_64 Fedora 8, the system call is implemented by instruction - syscall. The debug result is as fellow:
Dump of assembler code for function getuid:
0x00000036e7296220 <getuid+0>: mov $0x66,%eax 0x00000036e7296225 <getuid+5>: syscall 0x00000036e7296227 <getuid+7>: retq As far as I know, fast system call is implemented by sysenter on Intel CPU, and syscall on AMD CPU. Why the debug result is syscall, rather than sysenter?
If the HVM guest is x86_32 Fedora 8, can we set the system call implementation by sysenter? In x86_64 OS, is all system call is implemented by syscall?
Thank you for your response!
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-users] iptables support domU, Alberto Asuero Arroyo |
|---|---|
| Next by Date: | [Xen-users] Problem of installing Xen on Ubuntu 8.04.1: cannot find xen python modules, Ming Chen |
| Previous by Thread: | [Xen-users] iptables support domU, Alberto Asuero Arroyo |
| Next by Thread: | [Xen-users] Problem of installing Xen on Ubuntu 8.04.1: cannot find xen python modules, Ming Chen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
