From: Laurent Vivier <laurent@vivier.eu>
To: Tonis Tiigi <tonistiigi@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 2/2] linux-user: call set/getscheduler set/getparam directly
Date: Thu, 23 Dec 2021 21:37:12 +0100 [thread overview]
Message-ID: <e62f2cbf-0f38-bfb8-a01c-03fa84de5fdd@vivier.eu> (raw)
In-Reply-To: <20211223064728.18048-3-tonistiigi@gmail.com>
Le 23/12/2021 à 07:47, Tonis Tiigi a écrit :
> There seems to be difference in syscall and libc definition of these
> methods and therefore musl does not implement them (1e21e78bf7). Call
> syscall directly to ensure the behavior of the libc of user application,
> not the libc that was used to build QEMU.
>
> Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
> ---
> linux-user/syscall.c | 40 ++++++++++++++++++++++++++-------------
> linux-user/syscall_defs.h | 4 ++++
> 2 files changed, 31 insertions(+), 13 deletions(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 2f5a0fac5a..8c03a52a36 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -345,6 +345,17 @@ _syscall4(int, sys_sched_getattr, pid_t, pid, struct target_sched_attr *, attr,
> #define __NR_sys_sched_setattr __NR_sched_setattr
> _syscall3(int, sys_sched_setattr, pid_t, pid, struct target_sched_attr *, attr,
> unsigned int, flags);
> +#define __NR_sys_sched_getscheduler __NR_sched_getscheduler
> +_syscall1(int, sys_sched_getscheduler, pid_t, pid);
> +#define __NR_sys_sched_setscheduler __NR_sched_setscheduler
> +_syscall3(int, sys_sched_setscheduler, pid_t, pid, int, policy,
> + const struct target_sched_param *, param);
> +#define __NR_sys_sched_getparam __NR_sched_getparam
> +_syscall2(int, sys_sched_getparam, pid_t, pid,
> + struct target_sched_param *, param);
> +#define __NR_sys_sched_setparam __NR_sched_setparam
> +_syscall2(int, sys_sched_setparam, pid_t, pid,
> + const struct target_sched_param *, param);
> #define __NR_sys_getcpu __NR_getcpu
> _syscall3(int, sys_getcpu, unsigned *, cpu, unsigned *, node, void *, tcache);
> _syscall4(int, reboot, int, magic1, int, magic2, unsigned int, cmd,
> @@ -10555,30 +10566,32 @@ static abi_long do_syscall1(void *cpu_env, int num, abi_long arg1,
> return ret;
> case TARGET_NR_sched_setparam:
> {
> - struct sched_param *target_schp;
> - struct sched_param schp;
> + struct target_sched_param *target_schp;
> + struct target_sched_param schp;
You need to keep sched_param for schp as it is used with host syscall.
>
> if (arg2 == 0) {
> return -TARGET_EINVAL;
> }
> - if (!lock_user_struct(VERIFY_READ, target_schp, arg2, 1))
> + if (!lock_user_struct(VERIFY_READ, target_schp, arg2, 1)) {
> return -TARGET_EFAULT;
> + }
> schp.sched_priority = tswap32(target_schp->sched_priority);
> unlock_user_struct(target_schp, arg2, 0);
> - return get_errno(sched_setparam(arg1, &schp));
> + return get_errno(sys_sched_setparam(arg1, &schp));
> }
> case TARGET_NR_sched_getparam:
> {
> - struct sched_param *target_schp;
> - struct sched_param schp;
> + struct target_sched_param *target_schp;
> + struct target_sched_param schp;
You need to keep sched_param for schp as it is used with host syscall.
>
> if (arg2 == 0) {
> return -TARGET_EINVAL;
> }
> - ret = get_errno(sched_getparam(arg1, &schp));
> + ret = get_errno(sys_sched_getparam(arg1, &schp));
> if (!is_error(ret)) {
> - if (!lock_user_struct(VERIFY_WRITE, target_schp, arg2, 0))
> + if (!lock_user_struct(VERIFY_WRITE, target_schp, arg2, 0)) {
> return -TARGET_EFAULT;
> + }
> target_schp->sched_priority = tswap32(schp.sched_priority);
> unlock_user_struct(target_schp, arg2, 1);
> }
> @@ -10586,19 +10599,20 @@ static abi_long do_syscall1(void *cpu_env, int num, abi_long arg1,
> return ret;
> case TARGET_NR_sched_setscheduler:
> {
> - struct sched_param *target_schp;
> - struct sched_param schp;
> + struct target_sched_param *target_schp;
> + struct target_sched_param schp;
You need to keep sched_param for schp as it is used with host syscall.
> if (arg3 == 0) {
> return -TARGET_EINVAL;
> }
> - if (!lock_user_struct(VERIFY_READ, target_schp, arg3, 1))
> + if (!lock_user_struct(VERIFY_READ, target_schp, arg3, 1)) {
> return -TARGET_EFAULT;
> + }
> schp.sched_priority = tswap32(target_schp->sched_priority);
> unlock_user_struct(target_schp, arg3, 0);
> - return get_errno(sched_setscheduler(arg1, arg2, &schp));
> + return get_errno(sys_sched_setscheduler(arg1, arg2, &schp));
> }
> case TARGET_NR_sched_getscheduler:
> - return get_errno(sched_getscheduler(arg1));
> + return get_errno(sys_sched_getscheduler(arg1));
> case TARGET_NR_sched_getattr:
> {
> struct target_sched_attr *target_scha;
> diff --git a/linux-user/syscall_defs.h b/linux-user/syscall_defs.h
> index 310d6ce8ad..28b9fe9a47 100644
> --- a/linux-user/syscall_defs.h
> +++ b/linux-user/syscall_defs.h
> @@ -2928,4 +2928,8 @@ struct target_sched_attr {
> abi_uint sched_util_max;
> };
>
> +struct target_sched_param {
> + abi_int sched_priority;
> +};
> +
> #endif
Sorry, I missed these problem in my previous review.
Thanks,
Laurent
prev parent reply other threads:[~2021-12-23 20:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 6:47 [PATCH v3 0/2] linux-user: fixes for sched_ syscalls Tonis Tiigi
2021-12-23 6:47 ` [PATCH v3 1/2] linux-user: add sched_getattr support Tonis Tiigi
2021-12-23 21:03 ` Laurent Vivier
2021-12-23 23:00 ` Tõnis Tiigi
2022-01-03 17:07 ` Tõnis Tiigi
2022-01-03 18:37 ` Laurent Vivier
2022-01-03 19:31 ` Tõnis Tiigi
2022-01-03 22:17 ` Laurent Vivier
2021-12-23 6:47 ` [PATCH v3 2/2] linux-user: call set/getscheduler set/getparam directly Tonis Tiigi
2021-12-23 17:44 ` Laurent Vivier
2021-12-23 20:37 ` Laurent Vivier [this message]
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=e62f2cbf-0f38-bfb8-a01c-03fa84de5fdd@vivier.eu \
--to=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=tonistiigi@gmail.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).