* question about syscall interception
@ 2012-02-16 20:34 X
0 siblings, 0 replies; only message in thread
From: X @ 2012-02-16 20:34 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]
Hello everyone,
I have a few questions about syscall interception in Xen. Thanks for any
advice/suggestion.
Setting: CPU, Xen and PV Linux guest are all 64-bit
(1) If a guest app uses "syscall" instruction to launch a system call to
the guest kernel, is that behavior intercepted by Xen by default? If yes,
could someone please point me to the related code in Xen for this
interception? (anything to do with "switch_to_kernel in
xen/arch/x86/x86_64/entry.S"?) If no, then how could I intercept that
instruction in this case?
(2) If a guest app uses "int 0x80" to launch a system call, then is it true
that after "init_int80_direct_trap," the int 0x80 is no longer intercepted
by Xen, and the app can trap directly into the guest kernel? My
understanding is that "init_int80_direct_trap" initializes vcpu's
arch_vpuc.int80_bounce. Could someone please briefly explain how things
work after this struct is properly setup? How could I intercept system
calls launched in this way in Xen?
Thanks.
X
[-- Attachment #1.2: Type: text/html, Size: 1207 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-02-16 20:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-02-16 20:34 question about syscall interception X
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).