From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Gabriel Krisman Bertazi <gabriel@krisman.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] Create syscall groups for x86_64.
Date: Thu, 20 Nov 2014 03:08:00 -0000 [thread overview]
Message-ID: <87wq6qsh59.fsf@redhat.com> (raw)
In-Reply-To: <87r3wyoc5q.fsf@krisman.be> (Gabriel Krisman Bertazi's message of "Thu, 20 Nov 2014 00:09:53 -0200")
[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]
On Wednesday, November 19 2014, Gabriel Krisman Bertazi wrote:
> Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Sergio,
>
> Thank you for your review. I applied your suggestions and I will send
> the updated patches to this list in a few moments.
Thanks!
>> On Sunday, November 02 2014, Gabriel Krisman Bertazi wrote:
>>
>>> This commit introduces the following syscall groups for the x86_64
>>> architecture: memory, ipc, process, descriptor, signal and file.
>>>
>>> Please note that the sorting of the syscalls among these several groups
>>> follows the same structure used in strace.
>>>
>>> This also introduces tests for catching groups of syscalls on the x86_64
>>> architecture.
>>
>> I guess I said that before, but just in case I didn't: I would prefer if
>> this patch already updated the other architectures as well. IIUC you
>> are planning to do that in another series of patches, but it would be
>> good if you did everything at once, I think. However, I will not oppose
>> if you decide to touch only on x86_64 for now.
>
> Updating the syscall files by hand is quite error-prone and requires
> lots of typing. Should we bring PR 14276 to the table, it would also
> require extra work to update the groups later.
Yeah, I am aware of that :-/.
> A few weeks ago, you and I talked about writing a script to fix PR14276.
> What I want to do is to save me some typing now and update the other
> architectures only after we have such script to generate the syscall
> files, so we can use it to also generate the group information
> automatically. What do you think? Is that ok for you?
Heh, since you asked :-P...
My opinion is that writing this script could take some time, and I am
not counting on it be to ready soon, unfortunately.
That being said, I also don't think we should let the perfect be the
enemy of the good (I think Pedro said that once, and I liked the
phrase). Therefore, I am OK with your patch as is, provided we don't
take too long to start working on this script :-).
Thanks,
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
[-- Attachment #2: Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2014-11-20 3:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 19:36 [PATCH 0/4] Catch syscall groups Gabriel Krisman Bertazi
2014-11-02 19:36 ` [PATCH 2/4] Add support to catch groups of syscalls Gabriel Krisman Bertazi
2014-11-14 22:55 ` Sergio Durigan Junior
2014-11-02 19:36 ` [PATCH 1/4] Implemement support for groups of syscalls in the xml-syscall interface Gabriel Krisman Bertazi
2014-11-14 22:42 ` Sergio Durigan Junior
2014-11-02 19:37 ` [PATCH 4/4] Update documentation on catching a group of related syscalls Gabriel Krisman Bertazi
2014-11-02 19:45 ` Eli Zaretskii
2014-11-12 2:04 ` Gabriel Krisman Bertazi
2014-11-12 3:48 ` Eli Zaretskii
2014-11-14 18:52 ` Gabriel Krisman Bertazi
2014-11-14 20:38 ` Eli Zaretskii
2014-11-03 18:38 ` Sergio Durigan Junior
2014-11-02 19:37 ` [PATCH 3/4] Create syscall groups for x86_64 Gabriel Krisman Bertazi
2014-11-14 23:00 ` Sergio Durigan Junior
2014-11-20 2:11 ` Gabriel Krisman Bertazi
2014-11-20 3:08 ` Sergio Durigan Junior [this message]
2014-11-21 19:05 ` [PATCH v2 1/4] Implemement support for groups of syscalls in the xml-syscall interface Gabriel Krisman Bertazi
2014-11-29 0:19 ` [ping PATCH " Gabriel Krisman Bertazi
2014-12-08 0:09 ` [ping^2 " Gabriel Krisman Bertazi
2014-12-21 15:59 ` [ping^3 " Gabriel Krisman Bertazi
2015-01-12 20:47 ` Doug Evans
2015-01-15 8:03 ` [PATCH " Doug Evans
2015-01-29 4:43 ` Gabriel Krisman Bertazi
2015-01-29 7:42 ` Doug Evans
2014-11-21 19:05 ` [PATCH v2 2/4] Add support to catch groups of syscalls Gabriel Krisman Bertazi
2014-11-21 21:34 ` Sergio Durigan Junior
2015-01-15 8:12 ` Doug Evans
2014-11-21 19:06 ` [PATCH v2 4/4] Update documentation on catching a group of related syscalls Gabriel Krisman Bertazi
2014-11-21 19:48 ` Eli Zaretskii
2014-11-26 3:58 ` Gabriel Krisman Bertazi
2014-11-21 19:06 ` [PATCH v2 3/4] Create syscall groups for x86_64 Gabriel Krisman Bertazi
2015-01-15 8:28 ` Doug Evans
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=87wq6qsh59.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gabriel@krisman.be \
--cc=gdb-patches@sourceware.org \
/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