From: Tom Rini <trini@konsulko.com>
To: Sean Anderson <seanga2@gmail.com>
Cc: Quentin Schulz <quentin.schulz@cherry.de>,
Quentin Schulz <foss+uboot@0leil.net>,
Simon Glass <sjg@chromium.org>,
u-boot@lists.denx.de, Alexander Dahl <ada@thorsis.com>,
Bin Meng <bmeng.cn@gmail.com>,
Dario Binacchi <dariobin@libero.it>,
Ashok Reddy Soma <ashok.reddy.soma@amd.com>,
Michal Simek <michal.simek@amd.com>
Subject: Re: [PATCH v2 3/4] dm: core: migrate debug() messages to use dm_warn
Date: Wed, 2 Oct 2024 09:54:37 -0600 [thread overview]
Message-ID: <20241002155437.GP4737@bill-the-cat> (raw)
In-Reply-To: <b574fe29-3e3b-df51-6b09-af06303e11ac@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4112 bytes --]
On Wed, Oct 02, 2024 at 11:13:14AM -0400, Sean Anderson wrote:
> On 10/2/24 05:25, Quentin Schulz wrote:
> > Hi Alexander,
> >
> > On 10/2/24 10:37 AM, Alexander Dahl wrote:
> > > Hello Quentin,
> > >
> > > sorry for being late to the party, but I just tested v2024.10-rc6 and
> > > my console output looks like this now:
> > >
> > > ofnode_read_bool: bootph-all: true
> > > ofnode_read_u32_array: ranges: ofnode_read_bool: bootph-all: false
> > > ofnode_read_bool: bootph-some-ram: false
> > > ofnode_read_bool: bootph-pre-ram: false
> > > ofnode_read_bool: bootph-pre-sram: false
> > > ofnode_read_bool: u-boot,dm-pre-reloc: false
> > > ofnode_read_bool: u-boot,dm-pre-proper: false
> > > ofnode_read_bool: u-boot,dm-spl: false
> > > ofnode_read_bool: u-boot,dm-tpl: false
> > > ofnode_read_bool: u-boot,dm-vpl: false
> > > ofnode_read_bool: bootph-all: false
> > > ofnode_read_bool: bootph-some-ram: false
> > > ofnode_read_bool: bootph-pre-ram: false
> > > ofnode_read_bool: bootph-pre-sram: false
> > > ofnode_read_bool: u-boot,dm-pre-reloc: false
> > > ofnode_read_bool: u-boot,dm-pre-proper: false
> > > ofnode_read_bool: u-boot,dm-spl: false
> > > ofnode_read_bool: u-boot,dm-tpl: false
> > > ofnode_read_bool: u-boot,dm-vpl: false
> > > ofnode_read_bool: bootph-all: true
> > > ofnode_read_u32_array: ranges: ofnode_read_bool: bootph-all: true
> > > ofnode_read_u32_array: ranges: ofnode_read_bool: bootph-all: true
> > > ofnode_read_bool: bootph-all: true
> > > ofnode_read_bool: bootph-all: false
> > > …
> > >
> > > This goes on for several screen pages, and clutters the usual output.
> > > I first thought I messed up CONFIG_LOGLEVEL or CONFIG_LOG, but no.
> > > All I had done was setting CONFIG_DM_WARN …
> > >
> > > Am Tue, Jun 11, 2024 at 03:04:26PM +0200 schrieb Quentin Schulz:
> > > > From: Quentin Schulz <quentin.schulz@cherry.de>
> > > >
> > > > Prior to that, seeing the debug() messages required to enable DM_DEBUG
> > > > which defines DEBUG (and then _DEBUG) which in turn makes failing
> > > > assert() calls reset U-Boot which isn't necessarily what is desired.
> > > >
> > > > Instead, let's migrate to dm_warn which is using log_debug when unset or
> > > > log_warn when set.
> > > >
> > > > While at it, reword the DM_DEBUG symbol in Kconfig to explain what it
> > > > now actually does.
> > >
> > > CONFIG_DM_WARN currently reads like this:
> > >
> > > Enable this to see warnings related to driver model.
> > >
> > > Warnings may help with debugging, such as when expected devices do
> > > not bind correctly. If the option is disabled, dm_warn() is compiled
> > > out - it will do nothing when called.
> > >
> > > Instead of just useful warnings, users get debug messages all over the
> > > place now. Is this actually intended behaviour? Can this be fixed
> > > before v2024.10 release please?
> > >
> >
> > There are basically less than 3 working days left before v2024.10 is released and I'm inclined to say this is annoying rather than a bug, so I am not entirely sure this will 1) make it in time if we agree on a fix (needs to include review process in those 3 working days) 2) be acceptable for a late addition in the release cycle. Let's try though, maybe we can figure something out.
>
> This is a bug. Printing this many messages will have a major impact on boot times.
>
> A config going from "may print out a few more lines of extra info" to "firehose"
> is very surprising to users (as evidenced by Alexander's email).
>
> If you can't figure out which lines to disable, I recommend simply reverting the
> patch.
Checking this myself too, no platforms enable this by default. So I
believe we do need to improve the situation here, but I don't think we
need to revert this for release.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-10-02 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 13:04 [PATCH v2 0/4] dm: core: fix several debug messages and migrate debug() to dm_warn Quentin Schulz
2024-06-11 13:04 ` [PATCH v2 1/4] dm: core: fix misleading debug message when matching compatible Quentin Schulz
2024-06-11 18:51 ` Simon Glass
2024-06-11 13:04 ` [PATCH v2 2/4] dm: core: fix signedness in debug messages Quentin Schulz
2024-06-11 18:51 ` Simon Glass
2024-06-11 13:04 ` [PATCH v2 3/4] dm: core: migrate debug() messages to use dm_warn Quentin Schulz
2024-06-11 18:51 ` Simon Glass
2024-10-02 8:37 ` Alexander Dahl
2024-10-02 9:25 ` Quentin Schulz
2024-10-02 9:51 ` Alexander Dahl
2024-10-02 10:23 ` Quentin Schulz
2024-10-02 15:13 ` Sean Anderson
2024-10-02 15:54 ` Tom Rini [this message]
2024-10-02 22:55 ` Simon Glass
2024-06-11 13:04 ` [PATCH v2 4/4] dm: core: fix typo in SPL_DM_WARN prompt text Quentin Schulz
2024-06-11 18:52 ` Simon Glass
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=20241002155437.GP4737@bill-the-cat \
--to=trini@konsulko.com \
--cc=ada@thorsis.com \
--cc=ashok.reddy.soma@amd.com \
--cc=bmeng.cn@gmail.com \
--cc=dariobin@libero.it \
--cc=foss+uboot@0leil.net \
--cc=michal.simek@amd.com \
--cc=quentin.schulz@cherry.de \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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.