public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Hunt <johunt@akamai.com>
To: Josh Hunt <johunt@akamai.com>
Cc: "borislav.petkov@amd.com" <borislav.petkov@amd.com>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] amd64_edac: Memory size reported double on processor family 0Fh
Date: Tue, 11 Sep 2012 18:02:01 -0500	[thread overview]
Message-ID: <504FC2E9.4010708@akamai.com> (raw)
In-Reply-To: <1347403947-20187-1-git-send-email-johunt@akamai.com>

[fixing lkml address]

On 09/11/2012 05:52 PM, Josh Hunt wrote:
> With recent kernels we noticed that edac was reporting double the memory size on
> systems running with AMD family 0Fh processors. I'm not very familiar with the
> code, but this resolves it from what I can see on my systems. At least in
> amd64_debug_display_dimm_sizes() and k8_dbam_to_chip_select() there appeared
> to be redundant shifts to the left by 1 when WIDTH_128 is present.
>
> thanks
> Josh
>
> ---
>
> Since commit 41d8bfaba70311c2fa0666554ef160ea8ffc9daf the memory size reported
> by edac has been double. Adding to the shift if WIDTH_128 is set looks to be
> redundant, removing.
>
> Signed-off-by: Josh Hunt <johunt@akamai.com>
> ---
>   drivers/edac/amd64_edac.c |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c
> index 5a297a2..c796710 100644
> --- a/drivers/edac/amd64_edac.c
> +++ b/drivers/edac/amd64_edac.c
> @@ -1123,7 +1123,7 @@ static int k8_dbam_to_chip_select(struct amd64_pvt *pvt, u8 dct,
>
>   	if (pvt->ext_model >= K8_REV_F) {
>   		WARN_ON(cs_mode > 11);
> -		return ddr2_cs_size(cs_mode, dclr & WIDTH_128);
> +		return ddr2_cs_size(cs_mode, 0);
>   	}
>   	else if (pvt->ext_model >= K8_REV_D) {
>   		unsigned diff;
>


       reply	other threads:[~2012-09-11 23:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1347403947-20187-1-git-send-email-johunt@akamai.com>
2012-09-11 23:02 ` Josh Hunt [this message]
2012-09-12  8:51   ` [PATCH] amd64_edac: Memory size reported double on processor family 0Fh Borislav Petkov
2012-09-12 12:38     ` Josh Hunt
2012-09-12 12:52       ` Josh Hunt
2012-09-12 15:30         ` Borislav Petkov
2012-09-12 15:37           ` Josh Hunt
2012-09-12 15:49             ` Borislav Petkov
2012-09-12 16:23               ` Josh Hunt
2012-09-12 16:48                 ` Borislav Petkov
2012-09-12 16:58                   ` Josh Hunt
2012-09-12 17:06                     ` Borislav Petkov
2012-09-12 17:23                       ` Borislav Petkov
2012-09-14 12:55                         ` Josh Hunt
2012-09-14 14:39                           ` Josh Hunt
2012-09-14 15:40                             ` Borislav Petkov
2012-09-21 12:36                             ` Borislav Petkov
2012-09-21 13:02                               ` Josh Hunt
2012-09-21 14:01                                 ` Borislav Petkov
2012-09-21 14:54                                   ` Josh Hunt
2012-09-21 15:10                                     ` Borislav Petkov

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=504FC2E9.4010708@akamai.com \
    --to=johunt@akamai.com \
    --cc=borislav.petkov@amd.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.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