From: Jan Beulich <jbeulich@suse.com>
To: paul@xen.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v8 6/6] AMD/IOMMU: expose errors and warnings unconditionally
Date: Tue, 28 Sep 2021 09:50:55 +0200 [thread overview]
Message-ID: <707b7bdb-bf81-8c16-a7a9-f55256f53ec6@suse.com> (raw)
In-Reply-To: <ba9fe216-32a8-ef6d-173b-4f0d31a20db2@gmail.com>
On 28.09.2021 09:42, Durrant, Paul wrote:
> On 22/09/2021 15:38, Jan Beulich wrote:
>> Making these dependent upon "iommu=debug" isn't really helpful in the
>> field. Where touching respective code anyway also make use of %pp and
>> %pd.
>>
>> Requested-by: Andrew Cooper <andrew.cooper3@citrix.com>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> Reviewed-by: Paul Durrant <paul@xen.org>
Thanks.
>> @@ -515,14 +513,13 @@ static u16 __init parse_ivhd_device_rang
>> dev_length = sizeof(*range);
>> if ( header_length < (block_length + dev_length) )
>> {
>> - AMD_IOMMU_DEBUG("IVHD Error: Invalid Device_Entry Length!\n");
>> + AMD_IOMMU_ERROR("IVHD: invalid Device_Entry length\n");
>> return 0;
>> }
>>
>> if ( range->end.header.type != ACPI_IVRS_TYPE_END )
>> {
>> - AMD_IOMMU_DEBUG("IVHD Error: "
>> - "Invalid Range: End_Type %#x\n",
>> + AMD_IOMMU_ERROR("IVHD Error: invalid range: End_Type %#x\n",
>
> NIT: I guess you want to drop the 'Error' here like you did elsewhere.
Yes indeed. Fixed. Thanks for spotting.
Jan
prev parent reply other threads:[~2021-09-28 7:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 14:35 [PATCH v8 0/6] AMD/IOMMU: further work split from XSA-378 Jan Beulich
2021-09-22 14:36 ` [PATCH v8 1/6] AMD/IOMMU: obtain IVHD type to use earlier Jan Beulich
2021-09-28 7:12 ` Durrant, Paul
2021-10-19 23:34 ` Andrew Cooper
2021-10-20 6:58 ` Jan Beulich
2021-10-20 8:17 ` Jan Beulich
2021-09-22 14:37 ` [PATCH v8 2/6] AMD/IOMMU: improve (extended) feature detection Jan Beulich
2021-09-22 14:37 ` [PATCH v8 3/6] AMD/IOMMU: check IVMD ranges against host implementation limits Jan Beulich
2021-09-22 14:37 ` [PATCH v8 4/6] AMD/IOMMU: respect AtsDisabled device flag Jan Beulich
2021-09-28 7:34 ` Durrant, Paul
2021-09-28 7:47 ` Jan Beulich
2021-09-28 7:57 ` Durrant, Paul
2021-09-22 14:38 ` [PATCH v8 5/6] AMD/IOMMU: pull ATS disabling earlier Jan Beulich
2021-09-28 7:36 ` Durrant, Paul
2021-09-22 14:38 ` [PATCH v8 6/6] AMD/IOMMU: expose errors and warnings unconditionally Jan Beulich
2021-09-28 7:42 ` Durrant, Paul
2021-09-28 7:50 ` Jan Beulich [this message]
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=707b7bdb-bf81-8c16-a7a9-f55256f53ec6@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=paul@xen.org \
--cc=xen-devel@lists.xenproject.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.