From: Aravind <aravind.gopalakrishnan@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Doug Thompson <dougthompson@xmission.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
<linux-edac@vger.kernel.org>
Subject: Re: [PATCH] edac: Handle EDAC ECC errors for Family 16h
Date: Mon, 15 Apr 2013 13:59:32 -0500 [thread overview]
Message-ID: <516C4E14.1080708@amd.com> (raw)
In-Reply-To: <516C2EA2.1050806@amd.com>
On 04/15/2013 11:45 AM, Aravind wrote:
> On 04/15/2013 11:11 AM, Borislav Petkov wrote:
>> On Mon, Apr 15, 2013 at 09:56:08AM -0600, Bjorn Helgaas wrote:
>>> On Mon, Apr 15, 2013 at 9:17 AM, Aravind Gopalakrishnan
>>>> @@ -172,7 +176,12 @@
>>>> */
>>>> #define PCI_DEVICE_ID_AMD_15H_NB_F1 0x1601
>>>> #define PCI_DEVICE_ID_AMD_15H_NB_F2 0x1602
>>>> -
>>>> +#define PCI_DEVICE_ID_AMD_16H_NB_F0 0x1530
>>>> +#define PCI_DEVICE_ID_AMD_16H_NB_F1 0x1531
>>>> +#define PCI_DEVICE_ID_AMD_16H_NB_F2 0x1532
>>>> +#define PCI_DEVICE_ID_AMD_16H_NB_F3 0x1533
>>>> +#define PCI_DEVICE_ID_AMD_16H_NB_F4 0x1534
>>>> +#define PCI_DEVICE_ID_AMD_16H_NB_F5 0x1535
>>>>
>>>> /*
>>>> * Function 1 - Address Map
>>>> @@ -300,6 +309,7 @@ enum amd_families {
>>>> K8_CPUS = 0,
>>>> F10_CPUS,
>>>> F15_CPUS,
>>>> + F16_CPUS,
>>>> NUM_FAMILIES,
>>>> };
>>>>
>>>> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
>>>> index 1679ff6..59f732f 100644
>>>> --- a/include/linux/pci_ids.h
>>>> +++ b/include/linux/pci_ids.h
>>>> @@ -519,6 +519,8 @@
>>>> #define PCI_DEVICE_ID_AMD_11H_NB_LINK 0x1304
>>>> #define PCI_DEVICE_ID_AMD_15H_NB_F3 0x1603
>>>> #define PCI_DEVICE_ID_AMD_15H_NB_F4 0x1604
>>>> +#define PCI_DEVICE_ID_AMD_16H_NB_F3 0x1533
>>>> +#define PCI_DEVICE_ID_AMD_16H_NB_F4 0x1534
>>> What is the point of adding identical #defines both here and in
>>> amd64_edac.h? Also, read the note at the top of
>>> include/linux/pci_ids.h.
>> Yeah, they should be in pci_ids.h since they're used in amd_nb.c and
>> amd64_edac.c.
>>
>> But, what shouldn't be is adding unused defines (*_F0 and *_F5).
>> Aravind, please drop them.
>
> Yes, I have made the changes and sent it out as version 2 of the
> PATCH.
> Do have a look and let me know if I need to make any changes.
>
>
>> I'll review the rest of the patch when I get around to it this week.
>>
>
Correction: Fam16 does not support GART. I had mistakenly included
it in amd_nb.c (Apologies)
I have fixed it up and made few other cosmetic changes to the
patch. I have tested it once again to
make certain it works fine and it does..
Sending it out as V3 of the patch..
prev parent reply other threads:[~2013-04-15 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 15:17 [PATCH] edac: Handle EDAC ECC errors for Family 16h Aravind Gopalakrishnan
2013-04-15 15:56 ` Bjorn Helgaas
2013-04-15 16:11 ` Borislav Petkov
2013-04-15 16:45 ` Aravind
2013-04-15 18:59 ` Aravind [this message]
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=516C4E14.1080708@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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