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.

Signed-off-by: Keith Busch <keith.bu...@intel.com>
---
 drivers/acpi/hmat/hmat.c | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/drivers/acpi/hmat/hmat.c b/drivers/acpi/hmat/hmat.c
index b29f7160c7bb..6833c4897ff4 100644
--- a/drivers/acpi/hmat/hmat.c
+++ b/drivers/acpi/hmat/hmat.c
@@ -549,12 +549,27 @@ static __init void hmat_register_target_initiators(struct 
memory_target *target)
        }
 }
 
+static __init void hmat_register_target_perf(struct memory_target *target)
+{
+       unsigned mem_nid = pxm_to_node(target->memory_pxm);
+
+       if (!target->hmem_attrs.read_bandwidth &&
+           !target->hmem_attrs.read_latency &&
+           !target->hmem_attrs.write_bandwidth &&
+           !target->hmem_attrs.write_latency)
+               return;
+
+       node_set_perf_attrs(mem_nid, &target->hmem_attrs, 0);
+}
+
 static __init void hmat_register_targets(void)
 {
        struct memory_target *target;
 
-       list_for_each_entry(target, &targets, node)
+       list_for_each_entry(target, &targets, node) {
                hmat_register_target_initiators(target);
+               hmat_register_target_perf(target);
+       }
 }
 
 static __init void hmat_free_structures(void)
-- 
2.14.4

Reply via email to