From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
jbeulich@suse.com, suravee.suthikulpanit@amd.com,
xen-devel@lists.xen.org, keir@xen.org
Subject: Re: [PATCH V2] x86/AMD: Apply workaround for AMD F16h Erratum792
Date: Wed, 5 Feb 2014 21:27:52 +0000 [thread overview]
Message-ID: <52F2ACD8.9090902@citrix.com> (raw)
In-Reply-To: <1391636619-1703-1-git-send-email-Aravind.Gopalakrishnan@amd.com>
On 05/02/2014 21:43, Aravind Gopalakrishnan wrote:
> Workaround for the Erratum will be in BIOSes spun only after
> Jan 2014 onwards. But initial production parts shipped in 2013
> itself. Since there is a coverage hole, we should carry this fix
> in software in case BIOS does not do the right thing or someone
> is using old BIOS.
>
> Refer to Revision Guide for AMD F16h models 00h-0fh, document 51810
> Rev. 3.04, November2013 for details on the Erratum.
>
> Tested the patch on Fam16h server platform and it works fine.
>
> Changes in V2: (per Andrew.C comments)
> - Move pci_val into same scope
> - rework indentation to match linux style
>
> Signed-off-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
> Reviewed-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> xen/arch/x86/cpu/amd.c | 30 ++++++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/xen/arch/x86/cpu/amd.c b/xen/arch/x86/cpu/amd.c
> index 3307141..703bbda 100644
> --- a/xen/arch/x86/cpu/amd.c
> +++ b/xen/arch/x86/cpu/amd.c
> @@ -477,6 +477,36 @@ static void __devinit init_amd(struct cpuinfo_x86 *c)
> " all your (PV) guest kernels. ***\n");
>
> if (c->x86 == 0x16 && c->x86_model <= 0xf) {
> + /*
> + * Apply workaround for erratum 792
> + * Description:
> + * Processor does not ensure DRAM scrub read/write sequence
> + * is atomic wrt accesses to CC6 save state area. Therefore
> + * if a concurrent scrub read/write access is to same address
> + * the entry may appear as if it is not written. This quirk
> + * applies to Fam16h models 00h-0Fh
> + *
> + * See "Revision Guide" for AMD F16h models 00h-0fh,
> + * document 51810 rev. 3.04, Nov 2013
> + *
> + * Equivalent Linux patch link:
> + * http://marc.info/?l=linux-kernel&m=139066012217149&w=2
> + */
> + if (smp_processor_id() == 0) {
> + u32 pci_val;
> + pci_val = pci_conf_read32(0, 0, 0x18, 0x3, 0x58);
> + if (pci_val & 0x1f) {
> + pci_val &= ~0x1fu;
> + pci_conf_write32(0, 0, 0x18, 0x3, 0x58, pci_val);
> + }
> +
> + pci_val = pci_conf_read32(0, 0, 0x18, 0x3, 0x5c);
> + if (pci_val & 0x1) {
> + pci_val &= ~0x1u;
> + pci_conf_write32(0, 0, 0x18, 0x3, 0x5c, pci_val);
> + }
> + }
> +
> rdmsrl(MSR_AMD64_LS_CFG, value);
> if (!(value & (1 << 15))) {
> static bool_t warned;
next prev parent reply other threads:[~2014-02-05 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 21:43 [PATCH V2] x86/AMD: Apply workaround for AMD F16h Erratum792 Aravind Gopalakrishnan
2014-02-05 21:27 ` Andrew Cooper [this message]
2014-02-06 10:24 ` Jan Beulich
2014-02-06 19:11 ` Aravind Gopalakrishnan
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=52F2ACD8.9090902@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xen.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).