From: Borislav Petkov <bp@alien8.de>
To: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
Cc: dougthompson@xmission.com, m.chehab@samsung.com,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4] edac, amd64_edac: Modify usage of amd64_read_dct_pci_cfg()
Date: Mon, 15 Sep 2014 17:08:23 +0200 [thread overview]
Message-ID: <20140915150823.GH3340@nazgul.tnic> (raw)
In-Reply-To: <5416FDDA.2070208@amd.com>
On Mon, Sep 15, 2014 at 09:55:22AM -0500, Aravind Gopalakrishnan wrote:
> >>+ * Note: If ganging is enabled, barring the regs
> >>+ * F2x[1,0]98 and F2x[1,0]9C; reads reads to F2x1xx
> >Why aren't we dealing with those registers here then?
>
> According to BKDG, these registers are used to control DRAM electrical
> parameters..
> Afaict, we have never had to use these regs here..
... until someone decides to access them and copies the code here, which
would be wrong. Oh well, I guess someone will hopefully read the note
too, while copying...
> >> amd64_read_pci_cfg(pvt->F3, F10_ONLINE_SPARE, &pvt->online_spare);
> >>- amd64_read_dct_pci_cfg(pvt, DCLR0, &pvt->dclr0);
> >>- amd64_read_dct_pci_cfg(pvt, DCHR0, &pvt->dchr0);
> >>-
> >>- if (!dct_ganging_enabled(pvt)) {
> >>- amd64_read_dct_pci_cfg(pvt, DCLR1, &pvt->dclr1);
> >>- amd64_read_dct_pci_cfg(pvt, DCHR1, &pvt->dchr1);
> >>- }
> >>+ amd64_read_dct_pci_cfg(pvt, 0, DCLR0, &pvt->dclr0);
> >>+ amd64_read_dct_pci_cfg(pvt, 0, DCHR0, &pvt->dchr0);
> >> pvt->ecc_sym_sz = 4;
> >> if (pvt->fam >= 0x10) {
> >>+ amd64_read_dct_pci_cfg(pvt, 1, DCLR0, &pvt->dclr1);
> >>+ amd64_read_dct_pci_cfg(pvt, 1, DCHR0, &pvt->dchr1);
> >This doesn't look equivalent - above we're checking whether we're ganged
> >now you're doing it for >= F10h. Why?
> >
> >Because only F10h supports ganging?
>
> That's right.
> If ganging is enabled (which is a condition we check for in
> amd64_read_dct_pci_cfg();
> Then we return 0.
Right, but you're reading them now even if you don't have to. So why are
you even changing this? What's wrong with doing:
if (!dct_ganging_enabled(pvt)) {
amd64_read_dct_pci_cfg(pvt, 1, DCLR0, &pvt->dclr1);
amd64_read_dct_pci_cfg(pvt, 1, DCHR0, &pvt->dchr1);
}
which is much clearer than doing the family check.
--
Regards/Gruss,
Boris.
--
next prev parent reply other threads:[~2014-09-15 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 19:52 Aravind Gopalakrishnan
2014-09-15 12:09 ` Borislav Petkov
2014-09-15 14:55 ` Aravind Gopalakrishnan
2014-09-15 15:08 ` Borislav Petkov [this message]
2014-09-15 15:19 ` 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=20140915150823.GH3340@nazgul.tnic \
--to=bp@alien8.de \
--cc=aravind.gopalakrishnan@amd.com \
--cc=dougthompson@xmission.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.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
all inboxes | Powered by JetHome®