public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	x86@kernel.org, bp@suse.de, linux-kernel@vger.kernel.org,
	sherry.hurwitz@amd.com, hmh@hmh.eng.br, Kim.Naru@amd.com,
	Suravee.Suthikulpanit@amd.com
Subject: Re: [PATCH] x86, quirks: Add workaround for AMD F16h Erratum792
Date: Mon, 20 Jan 2014 08:07:24 +0100	[thread overview]
Message-ID: <20140120070724.GA31940@gmail.com> (raw)
In-Reply-To: <1389983973-3965-1-git-send-email-Aravind.Gopalakrishnan@amd.com>


* Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com> wrote:

> The workaround for this Erratum is included in AGESA. But BIOSes spun
> only after Jan2014 will have the fix (atleast server versions of the
> chip). The erratum affects both client and server platforms and since
> we cannot say with certainity that ALL BIOSes on systems out in the
> field will have the fix, we should probably insulate ourselves in case
> BIOS does not do the right thing or someone is using old BIOSes.
> 
> Refer 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 works fine.
> 
> Signed-off-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
> ---
>  arch/x86/kernel/quirks.c |   31 +++++++++++++++++++++++++++++++
>  1 file changed, 31 insertions(+)
> 
> diff --git a/arch/x86/kernel/quirks.c b/arch/x86/kernel/quirks.c
> index 04ee1e2..e55ae02 100644
> --- a/arch/x86/kernel/quirks.c
> +++ b/arch/x86/kernel/quirks.c
> @@ -571,3 +571,34 @@ DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_15H_NB_F5,
>  			quirk_amd_nb_node);
>  
>  #endif
> +
> +#if defined(CONFIG_PCI)
> +/*
> + * Apply AMD Fam16h Erratum792
> + * see Revision Guide for AMD F16h models 00h-0fh,
> + * document 51810 rev. 3.04, Nov 2013
> + */
> +static void quirk_amd_dram_scrub(struct pci_dev *dev)

The reference to the erratum is useful for people who want to see more 
details, but at least a short description of the problem being fixed 
and systems affected by the quirk is needed. 'DRAM scrub' is not very 
informative.

Thanks,

	Ingo

  reply	other threads:[~2014-01-20  7:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 18:39 [PATCH] x86, quirks: Add workaround for AMD F16h Erratum792 Aravind Gopalakrishnan
2014-01-20  7:07 ` Ingo Molnar [this message]
2014-01-21 19:32   ` Aravind Gopalakrishnan
2014-01-23 21:55     ` 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=20140120070724.GA31940@gmail.com \
    --to=mingo@kernel.org \
    --cc=Aravind.Gopalakrishnan@amd.com \
    --cc=Kim.Naru@amd.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=bp@suse.de \
    --cc=hmh@hmh.eng.br \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sherry.hurwitz@amd.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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