rsx: Lower some performance warnings to trace to reduce log spam

This commit is contained in:
kd-11
2024-02-11 02:20:19 +03:00
committed by Megamouse
parent c17014a055
commit c2631c914d
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -98,7 +98,7 @@ namespace gl
{ {
// This format is completely worthless to CPU processing algorithms where cache lines on die are linear. // This format is completely worthless to CPU processing algorithms where cache lines on die are linear.
// If this is happening, usually it means it was not a planned readback (e.g shared pages situation) // If this is happening, usually it means it was not a planned readback (e.g shared pages situation)
rsx_log.warning("[Performance warning] CPU readback of swizzled data"); rsx_log.trace("[Performance warning] CPU readback of swizzled data");
// Read-modify-write to avoid corrupting already resident memory outside texture region // Read-modify-write to avoid corrupting already resident memory outside texture region
std::vector<u8> tmp_data(rsx_pitch * height); std::vector<u8> tmp_data(rsx_pitch * height);
+1 -1
View File
@@ -323,7 +323,7 @@ namespace vk
{ {
// This format is completely worthless to CPU processing algorithms where cache lines on die are linear. // This format is completely worthless to CPU processing algorithms where cache lines on die are linear.
// If this is happening, usually it means it was not a planned readback (e.g shared pages situation) // If this is happening, usually it means it was not a planned readback (e.g shared pages situation)
rsx_log.warning("[Performance warning] CPU readback of swizzled data"); rsx_log.trace("[Performance warning] CPU readback of swizzled data");
// Read-modify-write to avoid corrupting already resident memory outside texture region // Read-modify-write to avoid corrupting already resident memory outside texture region
void* data = get_ptr(range.start); void* data = get_ptr(range.start);