Xen doesn't process them at all. The syscall trap causes the processor
to directly start executing guest-OS code --- Xen is not involved. If
you want to 'hook' application syscalls then this direct trap to guest
OS can be disabled, in which case syscall traps will pass via
do_general_protection_fault() in xen/arch/x86/traps.c.
-- Keir
> I am a newbie to Xen, please give me some basic idea and LET ME KNOW WHICH
> SOURCE CODE FILE maps to this procedure so that I can study the details.
> Thanks a lot!
>
> Xin
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel