[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAErSpo4MMJh9b0aivwGSbxCMVw24He1+Vo_LH0R0E+fYM5aThg@mail.gmail.com>
Date: Wed, 5 Mar 2014 14:24:12 -0700
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: suravee.suthikulpanit@....com
Cc: "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Aravind Gopalakrishnan <aravind.gopalakrishnan@....com>,
kim.naru@....com,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: Re: [PATCH 0/3] amd/pci: Add AMD hostbridge supports for newer AMD systems
[+cc linux-acpi]
On Wed, Mar 5, 2014 at 2:06 PM, <suravee.suthikulpanit@....com> wrote:
> From: Suravee Suthikulpanit <suravee.suthikulpanit@....com>
>
> The current code only supports upto AMD hostbridge for family11h.
> This causes PCI numa_node information to be reported incorrectly
> for newer family with multi sockets.
Where is the incorrect reporting? In ACPI tables? Is this patch a
way to cover up firmware defects in the ACPI description? Or is this
for machines without ACPI (it seems unlikely that machines with new
AMD processors would not have ACPI)?
The whole point of ACPI is that we shouldn't need to update the kernel
for new hardware, so if there's a firmware bug, it should be fixed, or
if the ACPI spec isn't powerful enough, it should be extended.
> This patch set introduces the logic to discover AMD hostbridges.
>
> Note:
> * Patch 1 and 2 are functional changes.
> * Patch 3 is code clean up/restructuring
>
> Suravee Suthikulpanit (3):
> amd/pci: Add supports for generic AMD hostbridges
> amd/pci: Support additional MMIO ranges capabilities
> amd/pci: Miscellaneous code clean up for early_fillup_mp_bus_info
>
> arch/x86/pci/amd_bus.c | 376 ++++++++++++++++++++++++++++++++----------------
> 1 file changed, 251 insertions(+), 125 deletions(-)
>
> --
> 1.7.10.4
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists