lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Norbert Lange <nolange79@gmail.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	lttng-dev <lttng-dev@lists.lttng.org>,
	paulmck <paulmck@kernel.org>
Subject: Re: [RFC PATCH liburcu] urcu-bp: introduce urcu_bp_disable_sys_membarrier()
Date: Fri, 22 Nov 2019 14:05:07 -0500 (EST)	[thread overview]
Message-ID: <833314385.1100.1574449507763.JavaMail.zimbra__30108.6577515647$1574449524$gmane$org@efficios.com> (raw)
In-Reply-To: <CADYdroNm8E6O2dWMzSsBPh3Hg12KO66kMPhqkyBWoAjgraFexg@mail.gmail.com>

----- On Nov 22, 2019, at 1:37 PM, Norbert Lange nolange79@gmail.com wrote:

> I still would like to propose having a compile time "off switch",
> cant see how this would work with preloaded libraries for one
> (lttng itself whips with multiple)

One option would be to introduce an environment variable that would
control this.

> 
> Cant tell for sure now, but a setup where "bulletproof Xenomai"
> libraries are used seems to better than special setup magic.
> If you have to do do alot measurements for finding rare hiccups,
> the last thing you want it figuring out you forget one config.

Indeed. I'm not sure what's the best way forward however.

Thanks,

Mathieu

> 
> Thanks for the speedy support, Norbert

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  parent reply	other threads:[~2019-11-22 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191122170040.23250-1-mathieu.desnoyers@efficios.com>
2019-11-22 17:02 ` [RFC PATCH liburcu] urcu-bp: introduce urcu_bp_disable_sys_membarrier() Mathieu Desnoyers
     [not found] ` <173739689.937.1574442178071.JavaMail.zimbra@efficios.com>
2019-11-22 18:37   ` Norbert Lange
     [not found]   ` <CADYdroNm8E6O2dWMzSsBPh3Hg12KO66kMPhqkyBWoAjgraFexg@mail.gmail.com>
2019-11-22 19:05     ` Mathieu Desnoyers [this message]
2019-11-22 17:00 Mathieu Desnoyers

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='833314385.1100.1574449507763.JavaMail.zimbra__30108.6577515647$1574449524$gmane$org@efficios.com' \
    --to=mathieu.desnoyers@efficios.com \
    --cc=jan.kiszka@siemens.com \
    --cc=lttng-dev@lists.lttng.org \
    --cc=nolange79@gmail.com \
    --cc=paulmck@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).