kernel/x86: Move the add_memory_type_range tracing to level "2".

We usually set level "1" by default, so this will hide it.
It's not really that useful when debugging problems in general
at this point.

OK'ed by tqh.
This commit is contained in:
Augustin Cavalier
2019-04-15 12:26:30 -04:00
parent 02f7c69828
commit b5d2337330
+2 -2
View File
@@ -561,7 +561,7 @@ add_memory_type_range(area_id areaID, uint64 base, uint64 size, uint32 type)
return B_BAD_VALUE;
}
TRACE_MTRR("add_memory_type_range(%" B_PRId32 ", %#" B_PRIx64 ", %#"
TRACE_MTRR2("add_memory_type_range(%" B_PRId32 ", %#" B_PRIx64 ", %#"
B_PRIx64 ", %" B_PRIu32 ")\n", areaID, base, size, type);
MutexLocker locker(sMemoryTypeLock);
@@ -614,7 +614,7 @@ remove_memory_type_range(area_id areaID)
memory_type_range* range = find_range(areaID);
if (range != NULL) {
TRACE_MTRR("remove_memory_type_range(%" B_PRId32 ", %#" B_PRIx64 ", %#"
TRACE_MTRR2("remove_memory_type_range(%" B_PRId32 ", %#" B_PRIx64 ", %#"
B_PRIx64 ", %" B_PRIu32 ")\n", range->area, range->base,
range->size, range->type);