From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: "Paul Menzel" <pmenzel@molgen.mpg.de>, "Jörg Rödel" <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org
Subject: Re: [PATCH] iommu/amd: Print extended features in one line to fix divergent log levels
Date: Wed, 17 Jun 2020 16:23:02 +0700 [thread overview]
Message-ID: <8250b9fa-b62b-7d80-d2b6-99b8587f4df4@amd.com> (raw)
In-Reply-To: <20200616220420.19466-1-pmenzel@molgen.mpg.de>
On 6/17/20 5:04 AM, Paul Menzel wrote:
> Currently, Linux logs the two messages below.
>
> [ 0.979142] pci 0000:00:00.2: AMD-Vi: Extended features (0xf77ef22294ada):
> [ 0.979546] PPR NX GT IA GA PC GA_vAPIC
>
> The log level of these lines differs though. The first one has level
> *info*, while the second has level *warn*, which is confusing.
>
> $ dmesg -T --level=info | grep "Extended features"
> [Tue Jun 16 21:46:58 2020] pci 0000:00:00.2: AMD-Vi: Extended features (0xf77ef22294ada):
> $ dmesg -T --level=warn | grep "PPR"
> [Tue Jun 16 21:46:58 2020] PPR NX GT IA GA PC GA_vAPIC
>
> The problem is, that commit 3928aa3f57 ("iommu/amd: Detect and enable
> guest vAPIC support") introduced a newline, causing `pr_cont()`, used to
> print the features, to default back to the default log level.
>
> /**
> * pr_cont - Continues a previous log message in the same line.
> * @fmt: format string
> * @...: arguments for the format string
> *
> * This macro expands to a printk with KERN_CONT loglevel. It should only be
> * used when continuing a log message with no newline ('\n') enclosed. Otherwise
> * it defaults back to KERN_DEFAULT loglevel.
> */
> #define pr_cont(fmt, ...) \
> printk(KERN_CONT fmt, ##__VA_ARGS__)
>
> So, remove the line break, so only one line is logged.
>
> Fixes: 3928aa3f57 ("iommu/amd: Detect and enable guest vAPIC support")
> Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
> Cc: iommu@lists.linux-foundation.org
> Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
> ---
> drivers/iommu/amd_iommu_init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iommu/amd_iommu_init.c b/drivers/iommu/amd_iommu_init.c
> index 5b81fd16f5faf8..8d9b2c94178c43 100644
> --- a/drivers/iommu/amd_iommu_init.c
> +++ b/drivers/iommu/amd_iommu_init.c
> @@ -1844,7 +1844,7 @@ static void print_iommu_info(void)
> pci_info(pdev, "Found IOMMU cap 0x%hx\n", iommu->cap_ptr);
>
> if (iommu->cap & (1 << IOMMU_CAP_EFR)) {
> - pci_info(pdev, "Extended features (%#llx):\n",
> + pci_info(pdev, "Extended features (%#llx):",
> iommu->features);
> for (i = 0; i < ARRAY_SIZE(feat_str); ++i) {
> if (iommu_feature(iommu, (1ULL << i)))
>
Reviewed-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Thanks,
Suravee
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-06-17 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 22:04 [PATCH] iommu/amd: Print extended features in one line to fix divergent log levels Paul Menzel
2020-06-17 9:23 ` Suravee Suthikulpanit [this message]
2020-06-30 9:52 ` Jörg Rödel
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=8250b9fa-b62b-7d80-d2b6-99b8587f4df4@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=pmenzel@molgen.mpg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox