From: Bart Van Assche <bvanassche@acm.org>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Zhengyuan Liu <liuzhengyuan@kylinos.cn>, mingo <mingo@kernel.org>,
"alexander.levin" <alexander.levin@microsoft.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: Compilation error for target liblockdep
Date: Tue, 14 Apr 2020 19:09:34 -0700 [thread overview]
Message-ID: <825bc318-cde1-f80c-972c-436a4fef4ecf@acm.org> (raw)
In-Reply-To: <SN4PR0401MB35983B3ACED57F66634CF90E9BDA0@SN4PR0401MB3598.namprd04.prod.outlook.com>
On 2020-04-14 06:08, Johannes Thumshirn wrote:
> These files aren't unit tests for lockdep, so they can't be converted to
> KUnit. liblockdep is a stand alone library bringing lockdep's
> functionallity to pthread via LDPRELOAD, see also:
> https://lwn.net/Articles/536363/
How big is the user base of liblockdep? How many alternatives exist for
liblockdep? Are these alternatives better or worse than liblockdep? See
also:
* https://clang.llvm.org/docs/ThreadSafetyAnalysis.html
* https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual
* http://valgrind.org/docs/manual/hg-manual.html
Bart.
prev parent reply other threads:[~2020-04-15 2:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 9:20 Compilation error for target liblockdep Zhengyuan Liu
2019-11-18 23:14 ` Bart Van Assche
[not found] ` <SN4PR0401MB359876ED2A2D503638658A679B1A0@SN4PR0401MB3598.namprd04.prod.outlook.com>
2020-02-14 5:57 ` Bart Van Assche
[not found] ` <SN4PR0401MB35983B3ACED57F66634CF90E9BDA0@SN4PR0401MB3598.namprd04.prod.outlook.com>
2020-04-15 2:09 ` Bart Van Assche [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=825bc318-cde1-f80c-972c-436a4fef4ecf@acm.org \
--to=bvanassche@acm.org \
--cc=Johannes.Thumshirn@wdc.com \
--cc=alexander.levin@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhengyuan@kylinos.cn \
--cc=mingo@kernel.org \
--cc=sashal@kernel.org \
/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).