From: Suravee Suthikulpanit <suravee.suthikulpanit-5C7GfCeVMHo@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: ssg.sos.staff-v4o/RmcJZDMz7H3ftjWMJQC/G2K4zDHf@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Udo van den Heuvel
<udovdh-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
Subject: Re: [PATCH 1/1] AMD Family15h Model10-1Fh erratum 746 Workaround
Date: Wed, 23 Jan 2013 09:07:17 -0600 [thread overview]
Message-ID: <50FFFCA5.1010309@amd.com> (raw)
In-Reply-To: <20130123070604.GT25591-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
On 1/23/2013 1:06 AM, Joerg Roedel wrote:
> On Tue, Jan 22, 2013 at 05:19:10PM -0600, Suthikulpanit, Suravee wrote:
>> From: Suravee Suthikulpanit <suravee.suthikulpanit-5C7GfCeVMHo@public.gmane.org>
>> @@ -1171,6 +1195,8 @@ static int iommu_init_pci(struct amd_iommu *iommu)
>> for (i = 0; i < 0x83; i++)
>> iommu->stored_l2[i] = iommu_read_l2(iommu, i);
>> }
>> +
>> + amd_iommu_apply_erratum_746(iommu);
> This will also be applied to RD890 IOMMUs, right? This workaround should
> be limited to Trinity IOMMUs.
Inside the function, it checks the family and model number. Only Trinitiy is affected.
Suravee
WARNING: multiple messages have this Message-ID (diff)
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: <iommu@lists.linux-foundation.org>,
Borislav Petkov <bp@alien8.de>, <linux-kernel@vger.kernel.org>,
Udo van den Heuvel <udovdh@xs4all.nl>,
<ssg.sos.staff@mpdtxmail.amd.com>
Subject: Re: [PATCH 1/1] AMD Family15h Model10-1Fh erratum 746 Workaround
Date: Wed, 23 Jan 2013 09:07:17 -0600 [thread overview]
Message-ID: <50FFFCA5.1010309@amd.com> (raw)
In-Reply-To: <20130123070604.GT25591@8bytes.org>
On 1/23/2013 1:06 AM, Joerg Roedel wrote:
> On Tue, Jan 22, 2013 at 05:19:10PM -0600, Suthikulpanit, Suravee wrote:
>> From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
>> @@ -1171,6 +1195,8 @@ static int iommu_init_pci(struct amd_iommu *iommu)
>> for (i = 0; i < 0x83; i++)
>> iommu->stored_l2[i] = iommu_read_l2(iommu, i);
>> }
>> +
>> + amd_iommu_apply_erratum_746(iommu);
> This will also be applied to RD890 IOMMUs, right? This workaround should
> be limited to Trinity IOMMUs.
Inside the function, it checks the family and model number. Only Trinitiy is affected.
Suravee
next prev parent reply other threads:[~2013-01-23 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 23:19 [PATCH 1/1] AMD Family15h Model10-1Fh erratum 746 Workaround suravee.suthikulpanit
2013-01-22 23:19 ` suravee.suthikulpanit
[not found] ` <1358896750-5199-1-git-send-email-suravee.suthikulpanit-5C7GfCeVMHo@public.gmane.org>
2013-01-23 7:06 ` Joerg Roedel
2013-01-23 7:06 ` Joerg Roedel
[not found] ` <20130123070604.GT25591-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2013-01-23 15:07 ` Suravee Suthikulpanit [this message]
2013-01-23 15:07 ` Suravee Suthikulpanit
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=50FFFCA5.1010309@amd.com \
--to=suravee.suthikulpanit-5c7gfcevmho@public.gmane.org \
--cc=bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ssg.sos.staff-v4o/RmcJZDMz7H3ftjWMJQC/G2K4zDHf@public.gmane.org \
--cc=udovdh-qWit8jRvyhVmR6Xm/wNWPw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.