From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Pipat/メタワニットポン ピパット" <methavanitpong.pipat@socionext.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Ruiyu Ni <ruiyu.ni@intel.com>, Eric Dong <eric.dong@intel.com>,
"Zeng, Star" <star.zeng@intel.com>
Subject: Re: MdeModulePkg/Bus/Sd/EmmcDxe: Too verbose debug print on read
Date: Tue, 5 Jun 2018 14:15:25 +0200 [thread overview]
Message-ID: <CAKv+Gu-vLZY5wV3kcbYasqZ-L1Ghc8mA8htnbJDh8=6UWmy4cA@mail.gmail.com> (raw)
In-Reply-To: <39667f5d35144426ace434f9dbd9adf6@SOC-EX03V.e01.socionext.com>
On 5 June 2018 at 13:45, <methavanitpong.pipat@socionext.com> wrote:
> Hi,
>
> My team is developing a board booting Linux from an on-board eMMC,
> and we find that EmmcReadWrite() debug print is too verbose for INFO level.
>
> // https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Bus/Sd/EmmcDxe/EmmcBlockIo.c#L904
> DEBUG ((EFI_D_INFO, "Emmc%a(): Part %d Lba ...
>
> Is this an intended level?
> I wonder if the level should be `DEBUG_BLKIO` instead.
>
I agree. I noticed the same, when loading GRUB, kernel and initrd from
eMMC, a significant amount of time is spent in these debug prints
next prev parent reply other threads:[~2018-06-05 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 11:45 MdeModulePkg/Bus/Sd/EmmcDxe: Too verbose debug print on read methavanitpong.pipat
2018-06-05 12:15 ` Ard Biesheuvel [this message]
2018-06-06 10:21 ` Zeng, Star
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-list 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='CAKv+Gu-vLZY5wV3kcbYasqZ-L1Ghc8mA8htnbJDh8=6UWmy4cA@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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