All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aristeu Rozanski <aris@redhat.com>
To: Seth Jennings <sjenning@redhat.com>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Tony Luck <tony.luck@intel.com>,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sb_edac: fix TAD presence check for sbridge_mci_bind_devs()
Date: Wed, 5 Aug 2015 14:20:36 -0400	[thread overview]
Message-ID: <20150805182036.GW23305@redhat.com> (raw)
In-Reply-To: <1438798561-10180-1-git-send-email-sjenning@redhat.com>

On Wed, Aug 05, 2015 at 01:16:01PM -0500, Seth Jennings wrote:
> In 7d375bff, NUM_CHANNELS was changed to 8 and the channel space was
> renumerated to handle EN, EP, and EX configurations.
> 
> The *_mci_bind_devs functions, except for sbridge_mci_bind_devs(), got a
> new device presence check in the form of saw_chan_mask.  However,
> sbridge_mci_bind_devs() still uses the NUM_CHANNELS for loop.
> 
> With the increase in NUM_CHANNELS, this loop fails at index 4 since
> SB only has 4 TADs.  This results in the following error on SB machines:
> 
> EDAC sbridge: Some needed devices are missing
> EDAC sbridge: Couldn't find mci handler
> EDAC sbridge: Couldn't find mci handle
> 
> This patch adapts the saw_chan_mask logic for sbridge_mci_bind_devs() as
> well.
> 
> After this patch:
> 
> EDAC MC0: Giving out device to module sbridge_edac.c controller Sandy Bridge Socket#0: DEV 0000:3f:0e.0 (POLLED)
> EDAC MC1: Giving out device to module sbridge_edac.c controller Sandy Bridge Socket#1: DEV 0000:7f:0e.0 (POLLED)

Acked-by: Aristeu Rozanski <aris@redhat.com>

> 
> Signed-off-by: Seth Jennings <sjenning@redhat.com>
> ---
>  drivers/edac/sb_edac.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/edac/sb_edac.c b/drivers/edac/sb_edac.c
> index ca78311..91cf710 100644
> --- a/drivers/edac/sb_edac.c
> +++ b/drivers/edac/sb_edac.c
> @@ -1648,6 +1648,7 @@ static int sbridge_mci_bind_devs(struct mem_ctl_info *mci,
>  {
>  	struct sbridge_pvt *pvt = mci->pvt_info;
>  	struct pci_dev *pdev;
> +	u8 saw_chan_mask = 0;
>  	int i;
>  
>  	for (i = 0; i < sbridge_dev->n_devs; i++) {
> @@ -1681,6 +1682,7 @@ static int sbridge_mci_bind_devs(struct mem_ctl_info *mci,
>  		{
>  			int id = pdev->device - PCI_DEVICE_ID_INTEL_SBRIDGE_IMC_TAD0;
>  			pvt->pci_tad[id] = pdev;
> +			saw_chan_mask |= 1 << id;
>  		}
>  			break;
>  		case PCI_DEVICE_ID_INTEL_SBRIDGE_IMC_DDRIO:
> @@ -1701,10 +1703,8 @@ static int sbridge_mci_bind_devs(struct mem_ctl_info *mci,
>  	    !pvt-> pci_tad || !pvt->pci_ras  || !pvt->pci_ta)
>  		goto enodev;
>  
> -	for (i = 0; i < NUM_CHANNELS; i++) {
> -		if (!pvt->pci_tad[i])
> -			goto enodev;
> -	}
> +	if (saw_chan_mask != 0x0f)
> +		goto enodev;
>  	return 0;
>  
>  enodev:
> -- 
> 2.4.3
> 

-- 
Aristeu


  reply	other threads:[~2015-08-05 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 18:16 [PATCH] sb_edac: fix TAD presence check for sbridge_mci_bind_devs() Seth Jennings
2015-08-05 18:20 ` Aristeu Rozanski [this message]
2015-08-05 19:18 ` Luck, Tony
2015-09-24 17:11 ` 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=20150805182036.GW23305@redhat.com \
    --to=aris@redhat.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=sjenning@redhat.com \
    --cc=tony.luck@intel.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 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.