linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Crystal Wood <crwood@redhat.com>
To: John Kacur <jkacur@redhat.com>, Khem Raj <raj.khem@gmail.com>
Cc: Clark Williams <williams@redhat.com>,
	rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH] sched_attr: Do not define for glibc >= 2.41
Date: Wed, 29 Jan 2025 17:39:57 -0600	[thread overview]
Message-ID: <6041e9688de0cc0fb676ce6b20291f7afb2b96d0.camel@redhat.com> (raw)
In-Reply-To: <06e5ea58-b30e-0a8b-c9e8-226e8c20d70d@redhat.com>

On Wed, 2025-01-29 at 16:54 -0500, John Kacur wrote:
> 
> On Tue, 28 Jan 2025, 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
> > 
> > Define sched_attr conditionally on SCHED_ATTR_SIZE_VER0
> > 
> > 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: Clark Williams <williams@redhat.com>
> > Cc: John Kacur <jkacur@redhat.com>
> > Cc: rt-users <linux-rt-users@vger.kernel.org>
> > ---
> >  src/include/rt-sched.h | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/src/include/rt-sched.h b/src/include/rt-sched.h
> > index 80171c7..9cf0e3a 100644
> > --- a/src/include/rt-sched.h
> > +++ b/src/include/rt-sched.h
> > @@ -42,6 +42,8 @@
> >  #define __NR_sched_getattr		275
> >  #endif
> >  
> > +/* sched_attr is not defined in glibc < 2.41 */
> > +#ifndef SCHED_ATTR_SIZE_VER0
> >  struct sched_attr {
> >  	uint32_t size;
> >  	uint32_t sched_policy;
> > @@ -68,4 +70,6 @@ int sched_getattr(pid_t pid,
> >  		  unsigned int size,
> >  		  unsigned int flags);
> >  
> > +#endif /* SCHED_ATTR_SIZE_VER0 */
> > +
> >  #endif /* __RT_SCHED_H__ */
> > 
> > 
> 
> Does the following fix your problem?
[snip]

> +#if ! __GLIBC_PREREQ(2, 41)

I'm not familiar with the norms surrounding use of this macro, but it's
generally better to test features than versions... what if this feature
gets backported into some distro's earlier-version-numbered glibc?

FWIW, it looks like QEMU went with the feature test approach:
https://patchwork.ozlabs.org/project/qemu-devel/patch/20241011054806.1014276-1-raj.khem@gmail.com/
https://patchwork.ozlabs.org/project/qemu-devel/patch/20241011193140.1047648-1-raj.khem@gmail.com/

Also, was that patch posted anywhere?  Just wondering if I've still got
problems with email filtering.

-Crystal


  reply	other threads:[~2025-01-29 23:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28 23:08 [PATCH] sched_attr: Do not define for glibc >= 2.41 Khem Raj
2025-01-28 23:08 ` Khem Raj
2025-01-29 21:54 ` John Kacur
2025-01-29 23:39   ` Crystal Wood [this message]
2025-01-30 16:00     ` John Kacur

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=6041e9688de0cc0fb676ce6b20291f7afb2b96d0.camel@redhat.com \
    --to=crwood@redhat.com \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=raj.khem@gmail.com \
    --cc=williams@redhat.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).