From: Cyril Hrubis <chrubis@suse.cz>
To: John Stultz <jstultz@google.com>
Cc: kernel-team@android.com,
Darren Hart <darren@os.amperecomputing.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/6] sched_football: Use atomic for ball
Date: Tue, 7 May 2024 11:35:55 +0200 [thread overview]
Message-ID: <Zjn1-1YRyZGIUtEP@yuki> (raw)
In-Reply-To: <CANDhNCq__ZY9w3Nse-+K+d9gyXhrOe_6oZ=X01x_HufZwQ_6ig@mail.gmail.com>
Hi!
> > Wouldn't it make more sense to use the include/tst_atomic.h now instead
> > of the functions from librttest.h. At least the version in the
> > tst_atomic.h have proper memory barries for load, fallback in the case
> > that compiler does not support __atomic_foo(), etc.
>
> I don't object, but trying to include tst_atomic.h causes lots of
> redefinition warnings for PACKAGE, PACKAGE_*, and VERSION which are
> also set from librttest.h -> realtime_config.h
>
> Suggestions on how to proceed there?
The problem obviously is that we have two different config.h files that
conflicts.
Given that there isn't much in the realtime/configure.ac and these
checks does not seem to be relevant anymore it would make sense just to
get rid of it.
What we check for:
PTHREAD_PRIO_INHERIT - likely required for LinuxThreads vs NPTL
exp10 - seems to be supported in glibc since 2.1
__sync_add_and_fetch() - not needed when include/tst_atomic.h is used
Other than that the realtime/configure.ac contains stale data such as
defunct email to the ltp sourceforge mailing list which should be
removed anyways.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-05-07 9:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 22:57 [LTP] [PATCH 0/6] sched_football: Re-add crazy fans and other cleanups John Stultz via ltp
2024-04-23 22:57 ` [LTP] [PATCH 1/6] sched_football: Drop use of sched_yeild() John Stultz via ltp
2024-04-23 22:57 ` [LTP] [PATCH 2/6] sched_football: Use atomic for ball John Stultz via ltp
2024-04-29 9:06 ` Cyril Hrubis
2024-04-29 22:56 ` John Stultz via ltp
2024-05-07 9:35 ` Cyril Hrubis [this message]
2024-06-24 10:45 ` Cyril Hrubis
2024-06-25 0:05 ` John Stultz via ltp
2024-06-25 3:15 ` Li Wang
2024-06-25 20:20 ` John Stultz via ltp
2024-06-26 2:26 ` Li Wang
2024-06-26 17:01 ` John Stultz via ltp
2024-06-27 3:32 ` Li Wang
2024-06-27 11:09 ` Cyril Hrubis
2024-06-27 18:01 ` John Stultz via ltp
2024-06-27 18:03 ` John Stultz via ltp
2024-06-28 8:12 ` Cyril Hrubis
2024-06-28 18:37 ` John Stultz via ltp
2024-04-23 22:58 ` [LTP] [PATCH 3/6] sched_football: Re-add the crazy fans to interrupt everyone John Stultz via ltp
2024-04-29 9:10 ` Cyril Hrubis
2024-04-29 23:06 ` John Stultz via ltp
2024-06-27 13:25 ` Martin Doucha
2024-06-27 13:34 ` Cyril Hrubis
2024-04-23 22:58 ` [LTP] [PATCH 4/6] sched_football: Add a sleep before the game begins to get into steady state John Stultz via ltp
2024-04-23 22:58 ` [LTP] [PATCH 5/6] sched_football: Add prctrl calls to set thread comms John Stultz via ltp
2024-04-23 22:58 ` [LTP] [PATCH 6/6] sched_football: Add trace_marker messages if we're tracing John Stultz via ltp
2024-04-29 9:17 ` Cyril Hrubis
2024-04-29 23:14 ` John Stultz via ltp
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=Zjn1-1YRyZGIUtEP@yuki \
--to=chrubis@suse.cz \
--cc=darren@os.amperecomputing.com \
--cc=jstultz@google.com \
--cc=kernel-team@android.com \
--cc=ltp@lists.linux.it \
/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