Blame 0004-OvmfPkg-increase-max-debug-message-length-to-512.patch

fdb3e75
From 04d5e4e3e7c8444dbb52784a2d71cf284c9e05a0 Mon Sep 17 00:00:00 2001
b0c3aff
From: Laszlo Ersek <lersek@redhat.com>
b0c3aff
Date: Thu, 20 Feb 2014 22:54:45 +0100
2941706
Subject: [PATCH] OvmfPkg: increase max debug message length to 512
b0c3aff
7ae6f15
Upstream prefers short debug messages (sometimes even limited to 80
7ae6f15
characters), but any line length under 512 characters is just unsuitable
7ae6f15
for effective debugging. (For example, config strings in HII routing,
7ae6f15
logged by the platform driver "OvmfPkg/PlatformDxe" on DEBUG_VERBOSE
7ae6f15
level, can be several hundred characters long.) 512 is an empirically good
7ae6f15
value.
7ae6f15
7ae6f15
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
b0c3aff
---
b0c3aff
 OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c | 2 +-
b0c3aff
 1 file changed, 1 insertion(+), 1 deletion(-)
b0c3aff
b0c3aff
diff --git a/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c b/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c
fdb3e75
index dffb20822d..0577c43c3d 100644
b0c3aff
--- a/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c
b0c3aff
+++ b/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c
7407978
@@ -21,7 +21,7 @@
b0c3aff
 //
b0c3aff
 // Define the maximum debug and assert message length that this library supports
b0c3aff
 //
b0c3aff
-#define MAX_DEBUG_MESSAGE_LENGTH  0x100
2e34e08
+#define MAX_DEBUG_MESSAGE_LENGTH  0x200
b0c3aff
 
7407978
 //
7407978
 // VA_LIST can not initialize to NULL for all compiler, so we use this to