From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Andreas Hartmann <andihartmann@freenet.de>, <linux-pci@vger.kernel.org>
Cc: Joerg Roedel <joro@8bytes.org>,
Bjorn Helgaas <helgaas@kernel.org>,
iommu <iommu@lists.linux-foundation.org>
Subject: Re: AMD-Vi: Unable to write to IOMMU perf counter.
Date: Thu, 4 Feb 2016 12:11:52 -0600 [thread overview]
Message-ID: <56B39468.7080902@amd.com> (raw)
In-Reply-To: <56B39009.90401@maya.org>
On 2/4/2016 11:53 AM, Andreas Hartmann wrote:
> On 02/04/2016 at 04:47 PM, Suravee Suthikulanit wrote:
>> Hi Andreas,
>>
>> On 2/4/2016 8:53 AM, Andreas Hartmann wrote:
>>> Hello!
>>>
>>> The following happens with Linux 4.4.1 during boot on an MSI A78M-E35
>>> board. Additionally, I attached the complete dmesg.
>>
>> I was working on upstreaming changes to the AMD IOMMU Perf to fix some
>> of the similar issue I saw on a different platform. Would you please
>> check to see if this patch series would fix this?
>>
>> https://lkml.org/lkml/2016/1/1/141
>
>
> This patchset seems to fix the problem.
>
> [ 1.264639] AMD-Vi: IOMMU performance counters supported
>
> But there seems to be a problem with the location of
> perf_event_amd_iommu.h in the patch - I had to fix the complete
> perf_event_amd_iommu.h related patches to get them applied to 4.4. and
> finally compiled.
>
>
> Thanks,
> Andreas
>
Ok, I'll clean up and resend this patch series. Thanks for testing.
Thanks,
Suravee
prev parent reply other threads:[~2016-02-04 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 14:53 AMD-Vi: Unable to write to IOMMU perf counter Andreas Hartmann
2016-02-04 15:23 ` Bjorn Helgaas
2016-02-05 6:37 ` Andreas Hartmann
2016-02-04 15:47 ` Suravee Suthikulanit
2016-02-04 17:53 ` Andreas Hartmann
2016-02-04 18:11 ` Suravee Suthikulanit [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=56B39468.7080902@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=andihartmann@freenet.de \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).