From: Joe Perches <joe@perches.com>
To: Lv Zheng <lv.zheng@intel.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <len.brown@intel.com>, Lv Zheng <zetalog@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 1/2] ACPI / EC: Cleanup logging/debugging splitter support.
Date: Thu, 12 Mar 2015 15:33:09 -0700 [thread overview]
Message-ID: <1426199589.2742.16.camel@perches.com> (raw)
In-Reply-To: <79307c846d7ca93d0423829b84cb0354e276fb73.1425019470.git.lv.zheng@intel.com>
On Fri, 2015-02-27 at 14:48 +0800, Lv Zheng wrote:
> This patch refines logging/debugging splitter support so that when DEBUG is
> disabled, splitters won't be visible in the kernel logs while they are
> still available for developers when DEBUG is enabled.
>
> This patch also refines the splitters to mark the following handling
> process boundaries:
> +++++: boundary of driver starting/stopping
> boundary of IRQ storming
> =====: boundary of transaction advancement
> *****: boundary of EC command
> boundary of EC query
> #####: boundary of EC _Qxx evaluation
trivia:
> diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
[]
> /* --------------------------------------------------------------------------
> + * Logging/Debugging
> + * -------------------------------------------------------------------------- */
> +
> +/*
> + * Splitters used by the developers to track the boundary of the EC
> + * handling processes.
> + */
It'd be nice to comment/document these 3 letter descriptions
a bit better here in the source code.
> +#ifdef DEBUG
> +#define EC_DBG_SEP " "
> +#define EC_DBG_DRV "+++++"
> +#define EC_DBG_STM "====="
> +#define EC_DBG_REQ "*****"
> +#define EC_DBG_EVT "#####"
Maybe:
#define EC_DBG_SEP " "
#define EC_DBG_DRV "+++++" /* drivers start/stop */
#define EC_DBG_STM "=====" /* irq storm */
#define EC_DBG_REQ "*****" /* ec command boundary */
#define EC_DBG_EVT "#####" /* EC _Qxx evaluation */
>
next prev parent reply other threads:[~2015-03-12 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 19:43 [PATCH] ACPI / EC: Remove non-standard log emphasis Scot Doyle
2015-02-18 6:18 ` Rafael J. Wysocki
2015-02-25 8:41 ` Zheng, Lv
2015-02-25 8:51 ` Zheng, Lv
2015-02-25 15:01 ` Scot Doyle
2015-02-25 22:55 ` Rafael J. Wysocki
2015-02-27 0:30 ` Zheng, Lv
2015-02-27 6:48 ` [PATCH 0/2] ACPI / EC: Enhance logging/debugging Lv Zheng
2015-02-27 6:48 ` [PATCH 1/2] ACPI / EC: Cleanup logging/debugging splitter support Lv Zheng
2015-03-12 22:33 ` Joe Perches [this message]
2015-02-27 6:48 ` [PATCH 2/2] ACPI / EC: Add GPE reference counting debugging messages Lv Zheng
2015-03-12 22:42 ` [PATCH 0/2] ACPI / EC: Enhance logging/debugging Rafael J. Wysocki
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=1426199589.2742.16.camel@perches.com \
--to=joe@perches.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=zetalog@gmail.com \
/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