From: Philippe Gerum <rpm@xenomai.org>
To: Hongzhan Chen <hongzhan.chen@intel.com>
Cc: xenomai@xenomai.org
Subject: Re: [PATCH] recipes-kernel: disable more debugs that influence latency performance
Date: Sat, 18 Sep 2021 10:10:36 +0200 [thread overview]
Message-ID: <87h7ei1eyr.fsf@xenomai.org> (raw)
In-Reply-To: <20210918010850.23821-1-hongzhan.chen@intel.com>
Hongzhan Chen via Xenomai <xenomai@xenomai.org> writes:
> For dovetail-based xenomai, max lat may drop from 203.800 us
> to 9.807 us in 10 hours stressed latency test on Maxtang 8565U board
> with lava test.
>
> diff --git a/recipes-kernel/linux/files/common_nodbg.cfg b/recipes-kernel/linux/files/common_nodbg.cfg
> index d7d87c5..29b3522 100644
> --- a/recipes-kernel/linux/files/common_nodbg.cfg
> +++ b/recipes-kernel/linux/files/common_nodbg.cfg
> @@ -1,2 +1,9 @@
> # CONFIG_IPIPE_DEBUG is not set
> # CONFIG_XENO_OPT_DEBUG is not set
> +# CONFIG_PROVE_LOCKING is not set
> +# CONFIG_DEBUG_RT_MUTEXES is not set
> +# CONFIG_DEBUG_SPINLOCK is not set
> +# CONFIG_DEBUG_MUTEXES is not set
> +# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
> +# CONFIG_DEBUG_RWSEMS is not set
> +# CONFIG_DEBUG_LOCK_ALLOC is not set
Maybe it's time to backport the evl-check utility [1] from xenomai4 to
xenomai3, this is a very simple kconfig checker which helps in detecting
problematic settings. One just feeds it with a set of constraints like
[2] in order to perform such detection. FWIW, this command is documented
here.
[1] https://source.denx.de/Xenomai/xenomai4/libevl/-/blob/master/utils/evl-check.c
[2]
https://source.denx.de/Xenomai/xenomai4/libevl/-/blob/master/utils/kconf-checklist.evl
[3] https://evlproject.org/core/commands/#evl-check-command
--
Philippe.
next prev parent reply other threads:[~2021-09-18 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 1:08 [PATCH] recipes-kernel: disable more debugs that influence latency performance Hongzhan Chen
2021-09-18 8:10 ` Philippe Gerum [this message]
2021-10-05 13:09 ` Jan Kiszka
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=87h7ei1eyr.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=hongzhan.chen@intel.com \
--cc=xenomai@xenomai.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.