From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 201753] AMD-Vi: Unable to write to IOMMU perf counter
Date: Fri, 27 Mar 2020 20:58:38 +0000 [thread overview]
Message-ID: <bug-201753-28872-8I7XbfdyG7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201753-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201753
Neil (ledufff@hotmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ledufff@hotmail.com
--- Comment #1 from Neil (ledufff@hotmail.com) ---
Similar finding:
[ 1.144340] pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf
counter.
[ 1.144456] pci 0000:00:00.2: can't derive routing for PCI INT A
[ 1.144457] pci 0000:00:00.2: PCI INT A: not connected
[ 1.144521] pci 0000:00:01.0: Adding to iommu group 0
[ 1.144774] pci 0000:00:01.2: Adding to iommu group 1
[ 1.145009] pci 0000:00:01.3: Adding to iommu group 2
[ 1.145245] pci 0000:00:01.6: Adding to iommu group 3
[ 1.145468] pci 0000:00:08.0: Adding to iommu group 4
[ 1.145677] pci 0000:00:08.1: Adding to iommu group 5
[ 1.145899] pci 0000:00:08.2: Adding to iommu group 4
[ 1.145924] pci 0000:00:14.0: Adding to iommu group 6
[ 1.146173] pci 0000:00:14.3: Adding to iommu group 6
[ 1.146224] pci 0000:00:18.0: Adding to iommu group 7
[ 1.146438] pci 0000:00:18.1: Adding to iommu group 7
[ 1.146464] pci 0000:00:18.2: Adding to iommu group 7
[ 1.146481] pci 0000:00:18.3: Adding to iommu group 7
[ 1.146498] pci 0000:00:18.4: Adding to iommu group 7
[ 1.146515] pci 0000:00:18.5: Adding to iommu group 7
[ 1.146542] pci 0000:00:18.6: Adding to iommu group 7
[ 1.146560] pci 0000:00:18.7: Adding to iommu group 7
[ 1.146598] pci 0000:01:00.0: Adding to iommu group 8
[ 1.146851] pci 0000:02:00.0: Adding to iommu group 9
[ 1.147143] pci 0000:03:00.0: Adding to iommu group 10
[ 1.147467] pci 0000:04:00.0: Adding to iommu group 11
[ 1.147606] pci 0000:04:00.0: Using iommu direct mapping
[ 1.147648] pci 0000:04:00.1: Adding to iommu group 12
[ 1.147875] pci 0000:04:00.2: Adding to iommu group 12
[ 1.147912] pci 0000:04:00.3: Adding to iommu group 12
[ 1.147941] pci 0000:04:00.4: Adding to iommu group 12
[ 1.147979] pci 0000:04:00.5: Adding to iommu group 12
[ 1.148015] pci 0000:04:00.6: Adding to iommu group 12
[ 1.148032] pci 0000:05:00.0: Adding to iommu group 4
[ 1.148310] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
[ 1.148311] pci 0000:00:00.2: AMD-Vi: Extended features (0x4f77ef22294ada):
[ 1.148312] PPR NX GT IA GA PC GA_vAPIC
--
You are receiving this mail because:
You are watching the assignee of the bug.
next parent reply other threads:[~2020-03-27 20:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-201753-28872@https.bugzilla.kernel.org/>
2020-03-27 20:58 ` bugzilla-daemon [this message]
2020-03-27 21:06 ` [Bug 201753] AMD-Vi: Unable to write to IOMMU perf counter bugzilla-daemon
2021-02-02 1:33 ` bugzilla-daemon
2021-02-06 3:42 ` bugzilla-daemon
2021-02-06 4:01 ` bugzilla-daemon
2021-02-10 19:52 ` bugzilla-daemon
2021-02-10 19:54 ` bugzilla-daemon
2021-02-11 18:03 ` bugzilla-daemon
2021-02-24 20:32 ` bugzilla-daemon
2021-02-25 17:54 ` bugzilla-daemon
2021-02-26 11:58 ` bugzilla-daemon
2021-02-26 13:28 ` bugzilla-daemon
2021-02-26 21:17 ` bugzilla-daemon
2021-02-27 15:21 ` bugzilla-daemon
2021-02-28 20:04 ` bugzilla-daemon
2021-03-03 18:24 ` bugzilla-daemon
2021-03-05 10:26 ` bugzilla-daemon
2021-03-08 10:46 ` bugzilla-daemon
2021-03-15 22:00 ` bugzilla-daemon
2021-03-16 11:14 ` bugzilla-daemon
2021-03-17 10:32 ` bugzilla-daemon
2021-03-18 1:22 ` bugzilla-daemon
2021-03-18 8:41 ` bugzilla-daemon
2021-03-18 16:41 ` bugzilla-daemon
2021-03-19 9:13 ` bugzilla-daemon
2021-03-19 9:56 ` bugzilla-daemon
2021-03-19 16:37 ` bugzilla-daemon
2021-03-19 20:43 ` bugzilla-daemon
2021-03-25 21:51 ` bugzilla-daemon
2021-08-26 8:42 ` bugzilla-daemon
2021-08-26 8:43 ` bugzilla-daemon
2021-10-01 19:54 ` bugzilla-daemon
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=bug-201753-28872-8I7XbfdyG7@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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