From: Borislav Petkov <bp@alien8.de>
To: Joerg Roedel <joro@8bytes.org>
Cc: suravee.suthikulpanit@amd.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] iommu/amd: Add logic to decode AMD IOMMU event flag
Date: Tue, 2 Apr 2013 16:40:37 +0200 [thread overview]
Message-ID: <20130402144037.GE5488@pd.tnic> (raw)
In-Reply-To: <20130402143335.GB15687@8bytes.org>
On Tue, Apr 02, 2013 at 04:33:36PM +0200, Joerg Roedel wrote:
> Hi Suravee,
>
> On Wed, Mar 27, 2013 at 06:51:23PM -0500, suravee.suthikulpanit@amd.com wrote:
> > From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
> >
> > Add logic to decode AMD IOMMU event flag based on information from AMD IOMMU specification.
> > This should simplify debugging IOMMU errors. Also, dump DTE information in additional cases.
>
> The patch in general makes sense to have, but I have a couple of
> comments.
While you guys are at it, can someone fix this too pls (ASUS board with
a PD on it).
[ 0.220342] [Firmware Bug]: AMD-Vi: IOAPIC[9] not in IVRS table
[ 0.220398] [Firmware Bug]: AMD-Vi: IOAPIC[10] not in IVRS table
[ 0.220451] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
[ 0.220506] AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-04-02 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 23:51 [PATCH 1/3] iommu/amd: Add logic to decode AMD IOMMU event flag suravee.suthikulpanit
2013-04-01 13:47 ` Suravee Suthikulanit
2013-04-02 14:33 ` Joerg Roedel
2013-04-02 14:39 ` Suravee Suthikulanit
2013-04-02 14:40 ` Borislav Petkov [this message]
2013-04-02 15:03 ` Joerg Roedel
2013-04-02 15:29 ` Borislav Petkov
2013-04-02 15:41 ` Suravee Suthikulpanit
2013-04-02 16:06 ` Joerg Roedel
2013-04-02 16:04 ` Joerg Roedel
2013-04-02 16:17 ` Borislav Petkov
2013-04-02 16:33 ` Joerg Roedel
2013-04-02 19:32 ` Borislav Petkov
2013-04-02 20:59 ` Joerg Roedel
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=20130402144037.GE5488@pd.tnic \
--to=bp@alien8.de \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suravee.suthikulpanit@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