From: Andi Kleen <andi@firstfloor.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Hui Zhu <teawater@gmail.com>, gdb@sourceware.org
Subject: Re: System call support in process record and replay
Date: Mon, 01 Jun 2009 07:14:00 -0000 [thread overview]
Message-ID: <874ov0e87w.fsf@basil.nowhere.org> (raw)
In-Reply-To: <83iqji529q.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 May 2009 13:11:13 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I have a question about general design of the system call support for
> the record/replay target, for systems whose system calls are entered
> through software interrupts.
>
> The following excerpt from i386-tdep.c shows the currently-only
> implementation, for Linux system calls entered via INT 80h:
Note on modern x86 systems Linux doesn't even use INT 80h anymore for
syscalls, but typically SYSENTER (or sometimes SYSCALL)
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-06-01 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 10:11 Eli Zaretskii
2009-05-30 21:13 ` Doug Evans
2009-05-31 5:58 ` Hui Zhu
2009-05-31 17:47 ` Mark Kettenis
2009-06-01 15:09 ` Eli Zaretskii
2009-06-01 19:29 ` Michael Snyder
2009-06-01 7:14 ` Andi Kleen [this message]
2009-06-01 7:19 ` Hui Zhu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874ov0e87w.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=teawater@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox