config: Fix parsing AddrRange parameters in read_config.py.

The format of AddrRange parameters was changed, but
config/example/read_config.py wasn't updated for the new format.

Change-Id: Ie0da7aaa47c827bacc2b4f7f44929efd868b8794
Reviewed-on: https://gem5-review.googlesource.com/6942
Reviewed-by: Jason Lowe-Power <jason@lowepower.com>
Maintainer: Jason Lowe-Power <jason@lowepower.com>

diff --git a/configs/example/read_config.py b/configs/example/read_config.py
index 830bdb8b19865a90ca335c011cc9faa5a592b2aa..a4f03aa8cb5ae1c58890517d17cb6ab2be053148 100644 (file)
--- a/configs/example/read_config.py
+++ b/configs/example/read_config.py
@@ -82,8 +82,12 @@ def tick_parser(cast=lambda i: i):
 
 def addr_range_parser(cls, flags, param):
     sys.stdout.flush()
-    low, high = param.split(':')
-    return m5.objects.AddrRange(long(low), long(high))
+    (low, high, intlv_high_bit, xor_high_bit,
+     intlv_bits, intlv_match) = param.split(':')
+    return m5.objects.AddrRange(
+        start=long(low), end=long(high),
+        intlvHighBit=long(intlv_high_bit), xorHighBit=long(xor_high_bit),
+        intlvBits=long(intlv_bits), intlvMatch=long(intlv_match))
 
 def memory_bandwidth_parser(cls, flags, param):
     # The string will be in tick/byte