From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
Cc: Laura Abbott <labbott-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Warning from AMD IOMMU performance counters
Date: Thu, 25 Feb 2016 15:57:16 +0100 [thread overview]
Message-ID: <20160225145716.GA18581@8bytes.org> (raw)
In-Reply-To: <20160223175113.GA3711-fF5Pk5pvG8Y@public.gmane.org>
On Tue, Feb 23, 2016 at 06:51:13PM +0100, Borislav Petkov wrote:
> On Tue, Feb 23, 2016 at 09:26:18AM -0800, Laura Abbott wrote:
> > It was an issue with build signing on the testers machine. Once that was
> > fixed it was confirmed that the patches did fix the issue.
>
> Btw, Joerg did come up with a minimal fix today:
>
> https://lkml.kernel.org/r/20160223121215.GA31151-zLv9SwRftAIdnm+yROfE0A@public.gmane.org
>
> in case you want to run it instead of that big patchset which is still
> being reviewed...
I just queued that small fix and tagged it for stable. Suravees patches
are too intrusive for that and better suited for v4.6.
Joerg
next prev parent reply other threads:[~2016-02-25 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 22:35 Warning from AMD IOMMU performance counters Laura Abbott
[not found] ` <56C798B8.6080009-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-02-22 1:52 ` Wan Zongshun
[not found] ` <56CA69C7.3050508-6ukY98dZOFrYtjvyW6yDsg@public.gmane.org>
2016-02-23 1:36 ` Laura Abbott
2016-02-23 17:26 ` Laura Abbott
[not found] ` <56CC963A.1080607-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-02-23 17:51 ` Borislav Petkov
[not found] ` <20160223175113.GA3711-fF5Pk5pvG8Y@public.gmane.org>
2016-02-25 14:57 ` Joerg Roedel [this message]
[not found] ` <20160225145716.GA18581-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-02-25 17:47 ` Laura Abbott
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=20160225145716.GA18581@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=labbott-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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).