From: Paul Menzel <pmenzel@molgen.mpg.de>
To: "Jörg Rödel" <joro@8bytes.org>
Cc: David Coe <david.coe@live.co.uk>,
Robert Richter <rrichter@amd.com>,
Mario Limonciello <mario.limonciello@dell.com>,
Alexander Monakov <amonakov@ispras.ru>,
iommu@lists.linux-foundation.org, Dell.Client.Kernel@dell.com
Subject: Re: AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada).
Date: Wed, 15 Sep 2021 00:15:33 +0200 [thread overview]
Message-ID: <38c22e95-aa19-4166-be8a-28749bfacd3e@molgen.mpg.de> (raw)
In-Reply-To: <YUCRC0CI7rWXt4VA@8bytes.org>
[Cc: +Mario from AMD]
Dear Jörg,
Am 14.09.21 um 14:09 schrieb Jörg Rödel:
> On Tue, Sep 14, 2021 at 11:10:57AM +0200, Paul Menzel wrote:
>> Linux 5.15-rc1 still warns about that (also with latest system firmware
>> 1.1.50).
>
> The reason is most likely that the latest firmware still reports a
> different EFR feature set in the IVRS table than the IOMMU reports in
> its EFR MMIO register.
What do you mean exactly? Only 0x400 is prepended. The rest of the
string is identical. What feature set would the 0x400 in the beginning be?
Anyway, it’d be great if AMD and Dell could take a look.
Kind regards,
Paul
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-09-14 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 18:07 AMD-Vi: [Firmware Warn]: EFR mismatch. Use IVHD EFR (0xf77ef22294ada : 0x400f77ef22294ada) Paul Menzel
2021-09-14 9:10 ` Paul Menzel
2021-09-14 12:09 ` Jörg Rödel
2021-09-14 22:15 ` Paul Menzel [this message]
2021-09-14 22:17 ` Paul Menzel
2021-09-15 8:30 ` Jörg Rödel
2021-09-15 8:42 ` Paul Menzel
2021-09-15 8:47 ` Jörg Rödel
2021-09-15 14:39 ` Paul Menzel
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=38c22e95-aa19-4166-be8a-28749bfacd3e@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=Dell.Client.Kernel@dell.com \
--cc=amonakov@ispras.ru \
--cc=david.coe@live.co.uk \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=mario.limonciello@dell.com \
--cc=rrichter@amd.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