System calls table on different architectures
What and why?
Linux kernel has a set of system calls (called syscalls in short) offered for userspace. Each architecture can support them but the numbers used for their identification can vary between archs.
And those numbers can be important for some projects (like Valgrind for example).
How to help?
Check issues list and work on any of them.
Where to see HTML table?
I keep a copy at https://marcin.juszkiewicz.com.pl/download/tables/syscalls.html page.
Python support
As a part of this project I provide code to get system call number/name and availability from Python level.
Usage
Please check "bin/syscall" script and files in "examples/" directory.
Why this project looks like python-syscalls one?
I needed to merge both projects to make it more manageable. Now all data is kept in one place so I do not need to synchronize it between projects.
The plan is to have some kind of CI which would handle updates.
1 maintainer
Metadata
1 maintainer
Release files for system-calls 7.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| system_calls-7.2.tar.gz | 57.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| system_calls-7.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 191.1 kB
Release files / system_calls-7.2.tar.gz
| Download URL | system_calls-7.2.tar.gz |
|---|---|
| Size | 57.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
68595dd6283995005663d7bd3b10f95ea4bf995b9f830339f63743bf81310b6c
|
|
BLAKE2b-256 checksum How to use checksums |
45f0a40213ed493863fef4f72e5e63454ff049381afe4d5cc475efc2060f5de9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency logRelease files / system_calls-7.2-py3-none-any.whl
| Download URL | system_calls-7.2-py3-none-any.whl |
|---|---|
| Size | 133.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c203e1f3524e5abc5e934f60bd479e7d01e3a8d1992265cd07c6e1fb7726fd7
|
|
BLAKE2b-256 checksum How to use checksums |
cc99659ae65dd214d7016a9edfa787aab6f7e4dcf9f52a029b46350ebfd38cf9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency logSecurity for system-calls 7.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for system_calls-7.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
