From: Paolo Bonzini <pbonzini@redhat.com>
To: Khem Raj <raj.khem@gmail.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH] sched_attr: Do not define for glibc >= 2.41
Date: Fri, 11 Oct 2024 11:08:49 +0200 [thread overview]
Message-ID: <2a543dd0-11e7-4357-97d9-31979a1a87ff@redhat.com> (raw)
In-Reply-To: <20241011054806.1014276-1-raj.khem@gmail.com>
On 10/11/24 07:48, Khem Raj wrote:
> glibc 2.41+ has added [1] definitions for sched_setattr and sched_getattr functions
> and struct sched_attr. Therefore, it needs to be checked for here as well before
> defining sched_attr
>
> Fixes builds with glibc/trunk
>
> [1] https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=21571ca0d70302909cf72707b2a7736cf12190a0;hp=298bc488fdc047da37482f4003023cb9adef78f8
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> Cc: Laurent Vivier <laurent@vivier.eu> (m
Hi, I think it would be better to test in meson.build (with
cc.has_type), as is already done in several other places in
linux-user/syscall.c.
Thanks,
Paolo
> ---
> linux-user/syscall.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 1354e75694..9e6eebbf1a 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -359,7 +359,13 @@ _syscall3(int, sys_sched_getaffinity, pid_t, pid, unsigned int, len,
> #define __NR_sys_sched_setaffinity __NR_sched_setaffinity
> _syscall3(int, sys_sched_setaffinity, pid_t, pid, unsigned int, len,
> unsigned long *, user_mask_ptr);
> -/* sched_attr is not defined in glibc */
> +/* sched_attr is not defined in glibc < 2.41 */
> +#include <stdio.h>
> +
> +#if defined(__GLIBC__) && defined(__GLIBC_MINOR__)
> +# if (__GLIBC__ > 2) || (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 41)
> + /* do nothing */
> +# else
> struct sched_attr {
> uint32_t size;
> uint32_t sched_policy;
> @@ -372,6 +378,8 @@ struct sched_attr {
> uint32_t sched_util_min;
> uint32_t sched_util_max;
> };
> +# endif
> +#endif
> #define __NR_sys_sched_getattr __NR_sched_getattr
> _syscall4(int, sys_sched_getattr, pid_t, pid, struct sched_attr *, attr,
> unsigned int, size, unsigned int, flags);
>
>
next prev parent reply other threads:[~2024-10-11 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 5:48 [PATCH] sched_attr: Do not define for glibc >= 2.41 Khem Raj
2024-10-11 9:08 ` Paolo Bonzini [this message]
2024-10-11 9:15 ` Laurent Vivier
2024-10-11 11:17 ` Paolo Bonzini
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=2a543dd0-11e7-4357-97d9-31979a1a87ff@redhat.com \
--to=pbonzini@redhat.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=raj.khem@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).