kernel/git/stable/linux.git/drivers/acpi/hmat/Kconfig, branch masterLinux kernel stable treehttps://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=master2019-11-07T14:43:38+00:00ACPI: NUMA: Establish a new drivers/acpi/numa/ directory2019-11-07T14:43:38+00:00Dan Williamsdan.j.williams@intel.com2019-11-07T01:42:55+00:00urn:sha1:c710fcc5d95a5e0d1648c40c0b101e198bfc3459
Currently hmat.c lives under an "hmat" directory which does not enhance
the description of the file. The initial motivation for giving hmat.c
its own directory was to delineate it as mm functionality in contrast to
ACPI device driver functionality.
As ACPI continues to play an increasing role in conveying
memory location and performance topology information to the OS take the
opportunity to co-locate these NUMA relevant tables in a combined
directory.
numa.c is renamed to srat.c and moved to drivers/acpi/numa/ along with
hmat.c.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
acpi/hmat: Register performance attributes2019-04-04T16:41:21+00:00Keith Buschkeith.busch@intel.com2019-03-11T20:56:04+00:00urn:sha1:8d59f5a2ca765f65fd86db86f233678c3770819f
Save the best performance access attributes and register these with the
memory's node if HMAT provides the locality table. While HMAT does make
it possible to know performance for all possible initiator-target
pairings, we export only the local pairings at this time.
Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Keith Busch <keith.busch@intel.com>
Tested-by: Brice Goglin <Brice.Goglin@inria.fr>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
acpi/hmat: Register processor domain to its memory2019-04-04T16:41:21+00:00Keith Buschkeith.busch@intel.com2019-03-11T20:56:03+00:00urn:sha1:665ac7e92757fb74d249b2817dd91b3d9439d0a0
If the HMAT Subsystem Address Range provides a valid processor proximity
domain for a memory domain, or a processor domain matches the performance
access of the valid processor proximity domain, register the memory
target with that initiator so this relationship will be visible under
the node's sysfs directory.
Since HMAT requires valid address ranges have an equivalent SRAT entry,
verify each memory target satisfies this requirement.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Signed-off-by: Keith Busch <keith.busch@intel.com>
Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Brice Goglin <Brice.Goglin@inria.fr>
Tested-by: Brice Goglin <Brice.Goglin@inria.fr>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
acpi/hmat: Parse and report heterogeneous memory2019-04-04T16:41:20+00:00Keith Buschkeith.busch@intel.com2019-03-11T20:55:59+00:00urn:sha1:3accf7ae37a96c3bf4b51999f3c395ac5ffcd6d4
Systems may provide different memory types and export this information
in the ACPI Heterogeneous Memory Attribute Table (HMAT). Parse these
tables provided by the platform and report the memory access and caching
attributes to the kernel messages.
Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Tested-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Signed-off-by: Keith Busch <keith.busch@intel.com>
Tested-by: Brice Goglin <Brice.Goglin@inria.fr>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>