From: Tom Hromatka <tom.hromatka@oracle.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Paul Moore <paul@paul-moore.com>,
Dhaval Giani <dhaval.giani@oracle.com>,
tom.hromatka@oracle.com
Subject: [QUESTION] powerpc, libseccomp, and spu
Date: Mon, 11 Feb 2019 11:54:24 -0700 [thread overview]
Message-ID: <df04c747-58c1-4757-b0ef-1ccea745defb@oracle.com> (raw)
PowerPC experts,
Paul Moore and I are working on the v2.4 release of libseccomp,
and as part of this work I need to update the syscall table for
each architecture.
I have incorporated the new ppc syscall.tbl into libseccomp, but
I am not familiar with the value of "spu" in the ABI column. For
example:
22 32 umount sys_oldumount
22 64 umount sys_ni_syscall
22 spu umount sys_ni_syscall
In libseccomp, we maintain a 32-bit ppc syscall table and a 64-bit
ppc syscall table. Do we also need to add a "spu" ppc syscall
table? Some clarification on the syscalls marked "spu" and "nospu"
would be greatly appreciated.
Thanks.
Tom
next reply other threads:[~2019-02-11 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 18:54 Tom Hromatka [this message]
2019-02-12 0:18 ` [QUESTION] powerpc, libseccomp, and spu Benjamin Herrenschmidt
2019-02-12 0:18 ` Benjamin Herrenschmidt
2019-02-12 0:36 ` Michael Ellerman
2019-02-12 14:50 ` Tom Hromatka
2019-02-13 21:19 ` Paul Moore
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=df04c747-58c1-4757-b0ef-1ccea745defb@oracle.com \
--to=tom.hromatka@oracle.com \
--cc=dhaval.giani@oracle.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paul@paul-moore.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).