From: Steven Rostedt <rostedt@goodmis.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Marcin Nowakowski <marcin.nowakowski@imgtec.com>,
Linux API <linux-api@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
open list <linux-kernel@vger.kernel.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall
Date: Tue, 30 Aug 2016 16:58:30 -0400 [thread overview]
Message-ID: <20160830165830.5e494c43@gandalf.local.home> (raw)
In-Reply-To: <CALCETrXA0XbYuqYzWMJA+KjFS31YL0cTVtrvCnmRY_GMK6oNpw@mail.gmail.com>
On Tue, 30 Aug 2016 12:53:53 -0700
Andy Lutomirski <luto@amacapital.net> wrote:
> Egads! OK, I see why this is a mess.
:-)
>
> I guess we should be creating the metadata from the syscall tables
> instead of from the syscall definitions, but I guess that's currently
> a nasty per-arch mess.
Yep.
>
> Could we at least have an array of (arch, nr) instead of just an array
> of nrs in the metadata?
I guess I'm not following you on what would be used for "arch".
-- Steve
next prev parent reply other threads:[~2016-08-30 20:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 9:30 [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall Marcin Nowakowski
2016-08-29 9:30 ` [PATCH 2/2] MIPS: set NR_syscall_tables appropriately Marcin Nowakowski
2016-09-27 12:04 ` Ralf Baechle
2016-09-28 6:58 ` Marcin Nowakowski
2016-08-29 23:55 ` [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall Andy Lutomirski
2016-08-30 8:14 ` Marcin Nowakowski
2016-08-30 18:52 ` Andy Lutomirski
2016-08-30 19:29 ` Steven Rostedt
2016-08-30 19:53 ` Andy Lutomirski
2016-08-30 20:58 ` Steven Rostedt [this message]
2016-08-30 21:45 ` Andy Lutomirski
2016-08-30 22:03 ` Steven Rostedt
2016-08-30 22:08 ` Andy Lutomirski
2016-08-30 22:30 ` Steven Rostedt
2016-08-30 23:09 ` Andy Lutomirski
2016-08-30 23:28 ` Steven Rostedt
2016-08-31 0:01 ` Andy Lutomirski
2016-08-31 14:08 ` Marcin Nowakowski
2016-08-31 7:00 ` Marcin Nowakowski
2016-08-31 8:24 ` Arnd Bergmann
2016-09-01 15:24 ` Steven Rostedt
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=20160830165830.5e494c43@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=luto@amacapital.net \
--cc=marcin.nowakowski@imgtec.com \
--cc=mingo@redhat.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 NNTP newsgroup(s).