From: gilles.chanteperdrix@xenomai.org (Gilles Chanteperdrix)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Unset LOCKDEP and TRACE_IRQFLAGS_SUPPORT
Date: Fri, 2 Oct 2015 19:09:54 +0200 [thread overview]
Message-ID: <20151002170954.GU31137@hermes.click-hack.org> (raw)
In-Reply-To: <CAJfuBxwb0ZkfnVKZ+VrZCaD+1US3Zyh_is4YqFwaSFiiAoo=gw@mail.gmail.com>
On Fri, Oct 02, 2015 at 09:56:39AM -0600, Jim Cromie wrote:
> On Sun, Sep 27, 2015 at 8:52 AM, <Valdis.Kletnieks@vt.edu> wrote:
>
> > On Sun, 27 Sep 2015 15:08:57 +1300, vibnwis said:
> >
> > > Xenomai patching succeeded but when running one of is test apps,
> > "latency"
> > > showing
> > > > > > > > > >> > 0"000.000| BUG in low_init(): [main] mlockall: Cannot
> > > allocate
> > > > > > > memory
> > > And the mailing list member suggested the following
> >
> > Is that in dmesg, or output from the test program?
> > Is there more output, or is that it?
> >
> > Personally, if TRACE_IRQFLAGS is causing an issue with mlock, I'd suspect
> > a very buggy patch indeed. If it can't tolerate a trace function being
> > turned on, there;s probably some very questionable coding in there.....
> >
> >
>
> FWIW, I think Xenomai is far better smelling than your quick sniff has told
> your olfactory sensors
Actually, I think the following answer on the xenomai mailing list:
http://xenomai.org/pipermail/xenomai/2015-September/035126.html
Should make clear the fact that the answer about TRACE_IRQFLAGS was
an answer to the errors in the kernel log, not an answer to the
issue with mlockall.
--
Gilles.
https://click-hack.org
prev parent reply other threads:[~2015-10-02 17:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 14:16 Unset LOCKDEP and TRACE_IRQFLAGS_SUPPORT vibnwis
2015-09-26 16:03 ` Valdis.Kletnieks at vt.edu
2015-09-26 23:06 ` vibnwis
2015-09-27 0:54 ` Valdis.Kletnieks at vt.edu
2015-09-27 1:09 ` vibnwis
2015-09-27 1:53 ` Valdis.Kletnieks at vt.edu
2015-09-27 2:08 ` vibnwis
2015-09-27 6:00 ` vibnwis
2015-09-27 14:56 ` Valdis.Kletnieks at vt.edu
2015-09-27 14:52 ` Valdis.Kletnieks at vt.edu
2015-09-27 20:58 ` vibnwis
2015-09-27 22:22 ` Valdis.Kletnieks at vt.edu
2015-09-27 22:42 ` vibnwis
2015-09-28 0:17 ` Valdis.Kletnieks at vt.edu
2015-10-02 15:56 ` Jim Cromie
2015-10-02 16:11 ` Gilles Chanteperdrix
2015-10-02 21:43 ` Valdis.Kletnieks at vt.edu
2015-10-03 6:47 ` Gilles Chanteperdrix
2015-10-03 12:33 ` vibnwis
2015-10-03 13:11 ` Gilles Chanteperdrix
2015-10-05 1:24 ` vibnwis
2015-10-05 6:07 ` Gilles Chanteperdrix
2015-10-05 7:56 ` vibnwis
2015-10-05 7:07 ` Gilles Chanteperdrix
2015-10-05 7:54 ` vibnwis
2015-10-05 8:19 ` Gilles Chanteperdrix
2015-10-03 13:13 ` Gilles Chanteperdrix
2015-10-02 17:09 ` Gilles Chanteperdrix [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=20151002170954.GU31137@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.