From: "Jörg Rödel" <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Paul Menzel
<pmenzel+linux-iommu-KUpvgZVWgV9o1qOY/usvUg@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: MSI B350M MORTAR: `AMD-Vi: Unable to write to IOMMU perf counter.` and `pci 0000:00:00.2: can't derive routing for PCI INT A`
Date: Fri, 27 Jul 2018 10:27:54 +0200 [thread overview]
Message-ID: <20180727082754.hk44xktdydduu3qo@8bytes.org> (raw)
In-Reply-To: <d2c5ee4a-e72b-672e-ae30-7b3cd5a43c63-KUpvgZVWgV9o1qOY/usvUg@public.gmane.org>
Hi Paul,
On Mon, Jul 23, 2018 at 12:09:37PM +0200, Paul Menzel wrote:
> > or the BIOS did not enable the performance counter feature in the IOMMU
> > hardware.
>
> Is it possible to check that from the OS side?
It would be if we had the NB documentation, but I guess those details
are not publicly available.
> > Are you running on the latest BIOS?
>
> Yes, I am even using a “beta“ one from [1].
>
> DMI: MSI MS-7A37/B350M MORTAR (MS-7A37), BIOS 1.G1 05/17/2018
I think the best you can do is to report this as a bug to your BIOS
vendor and hope they'll fix it.
Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2018-07-27 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 16:02 MSI B350M MORTAR: `AMD-Vi: Unable to write to IOMMU perf counter.` and `pci 0000:00:00.2: can't derive routing for PCI INT A` Paul Menzel
2018-07-20 12:31 ` Jörg Rödel
[not found] ` <20180720123153.GC18541-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2018-07-23 10:09 ` Paul Menzel
[not found] ` <d2c5ee4a-e72b-672e-ae30-7b3cd5a43c63-KUpvgZVWgV9o1qOY/usvUg@public.gmane.org>
2018-07-27 8:27 ` Jörg Rödel [this message]
2018-07-27 9:18 ` Paul Menzel
2018-07-27 10:27 ` 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=20180727082754.hk44xktdydduu3qo@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pmenzel+linux-iommu-KUpvgZVWgV9o1qOY/usvUg@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).