From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] i2c-core: fix for dep-lock validator
Date: Fri, 7 Sep 2012 20:07:38 +0200 [thread overview]
Message-ID: <20120907200738.54efd8f3@endymion.delvare> (raw)
In-Reply-To: <20120907162032.140f0419-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
On Fri, 7 Sep 2012 16:20:32 +0200, Jean Delvare wrote:
> As far as performance is concerned, I thought about storing the depth
> value in struct i2c_adapter, but in fact I suspect the call to
> i2c_adapter_depth(adap) will be dropped at compilation time if
> CONFIG_PROVE_LOCKING isn't set, so the overhead should be zero.
I confirm the nonexistent overhead, except that the relevant
configuration option isn't CONFIG_PROVE_LOCKING but
CONFIG_DEBUG_LOCK_ALLOC. I think this is acceptable, that's not an
option distribution kernels would enable.
--
Jean Delvare
next prev parent reply other threads:[~2012-09-07 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 12:04 [PATCH] i2c-core: fix for dep-lock validator Michael Lawnick
[not found] ` <50473FC9.6000203-Mmb7MZpHnFY@public.gmane.org>
2012-09-07 13:00 ` Michael Lawnick
[not found] ` <5049F005.2040300-Mmb7MZpHnFY@public.gmane.org>
2012-09-07 13:28 ` Jean Delvare
[not found] ` <20120907152840.4de537b3-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-09-07 13:58 ` Michael Lawnick
[not found] ` <5049FD7E.9080709-Mmb7MZpHnFY@public.gmane.org>
2012-09-07 14:20 ` Jean Delvare
[not found] ` <20120907162032.140f0419-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-09-07 18:07 ` Jean Delvare [this message]
2012-09-07 20:51 ` Jean Delvare
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=20120907200738.54efd8f3@endymion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ml.lawnick-Mmb7MZpHnFY@public.gmane.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).