From: Tonis Tiigi <tonistiigi@gmail.com>
To: qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>
Cc: Tonis Tiigi <tonistiigi@gmail.com>
Subject: [PATCH 0/2] linux-user: fixes for sched_ syscalls
Date: Fri, 10 Dec 2021 18:27:48 -0800 [thread overview]
Message-ID: <20211211022749.95384-1-tonistiigi@gmail.com> (raw)
This patchset improves support for sched_* syscalls under user emulation. The first commit adds support for sched_g/setattr that was previously not implemented. There is no equivalent for these syscalls in libc, so I needed to redefine the struct from kernel. It can't be included directly because of conflict with libc sched headers.
The second commit fixes sched_g/setscheduler and sched_g/setparam, when QEMU is built with musl. Musl does not implement these due to conflict between what these functions should do in syscalls and libc https://git.musl-libc.org/cgit/musl/commit/?id=1e21e78bf7a5c24c217446d8760be7b7188711c2 . I've changed it to call syscall directly what should always be the expected behavior for the user.
Via https://github.com/tonistiigi/binfmt/pull/70 with additional tests.
Tonis Tiigi (2):
linux-user: add sched_getattr support
linux-user: call set/getscheduler set/getparam directly
linux-user/syscall.c | 71 ++++++++++++++++++++++++++++++++++++---
linux-user/syscall_defs.h | 15 +++++++++
2 files changed, 82 insertions(+), 4 deletions(-)
--
2.30.1 (Apple Git-130)
next reply other threads:[~2021-12-11 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 2:27 Tonis Tiigi [this message]
2021-12-11 2:27 ` [PATCH 1/2] linux-user: add sched_getattr support Tonis Tiigi
2021-12-19 17:09 ` Laurent Vivier
2021-12-11 2:27 ` [PATCH 2/2] linux-user: call set/getscheduler set/getparam directly Tonis Tiigi
2021-12-19 17:19 ` Laurent Vivier
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=20211211022749.95384-1-tonistiigi@gmail.com \
--to=tonistiigi@gmail.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).