From: Andrew Cagney <cagney@redhat.com>
To: Yao Qi <qiyaoltc@cn.ibm.com>
Cc: frysk@sourceware.org
Subject: Re: [patch ping] Cache system call number
Date: Mon, 13 Nov 2006 21:51:00 -0000 [thread overview]
Message-ID: <4558E8B8.5050403@redhat.com> (raw)
In-Reply-To: <20061102095945.GH3020@GreenHouse.cn.ibm.com>
Yao Qi wrote:
> On Tue, Oct 31, 2006 at 11:39:26AM -0500, Andrew Cagney wrote:
>
>> Yao, have the options:
>>
>> - make signal # an explict syscall-entry parameter
>> - make signal class an explicit syscall-entry parameter
>>
>
> Hi, Andrew,
> I am confused by "signal" here. Do you mean "signal" == "syscall"?
>
Yao, yes, sorry system call number, vis:
updateSyscallEnter (Task task, int syscallNumber)
That way all observers of system calls would be, as part of the entry,
be directly notified of which system call is involved; and during exit
that information would clearly not be involved. The client can then
decided if it wants to retain the value.
Andrew
prev parent reply other threads:[~2006-11-13 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 11:53 qiyaoltc
2006-10-31 16:39 ` Andrew Cagney
2006-11-02 10:02 ` Yao Qi
2006-11-13 21:51 ` Andrew Cagney [this message]
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=4558E8B8.5050403@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=qiyaoltc@cn.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).