From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 0/2] Allow to compile on archs without atomic support
Date: Wed, 10 Jan 2018 12:09:46 +0100 [thread overview]
Message-ID: <20180110110946.GC18314@rei> (raw)
In-Reply-To: <754978231.4598218.1515424172751.JavaMail.zimbra@redhat.com>
Hi!
> What if we made general implementation with some locking? It would be
> slower, but I think we don't use atomics that much for it to matter.
Atomic increment was easiest way how to make the test library thread
safe I wasn't concerned with speed at all. But that is not true for the
CVE tests which use atomic operation to synchronize threads to trigger
races.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-01-10 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 20:42 [LTP] [RFC PATCH 0/2] Allow to compile on archs without atomic support Petr Vorel
2018-01-04 20:42 ` [LTP] [RFC PATCH 1/2] tst_atomic.h: " Petr Vorel
2018-01-04 20:42 ` [LTP] [RFC PATCH 2/2] lib/tst_test.c: Don't print results on archs without atomic Petr Vorel
2018-01-08 15:09 ` [LTP] [RFC PATCH 0/2] Allow to compile on archs without atomic support Jan Stancek
2018-01-09 0:02 ` Petr Vorel
2018-01-10 11:09 ` Cyril Hrubis [this message]
2018-01-10 11:17 ` Petr Vorel
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=20180110110946.GC18314@rei \
--to=chrubis@suse.cz \
--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