From c19481cb9056a37a35e8fd5c0b22cb9dee5ec06d Mon Sep 17 00:00:00 2001 From: Laszlo Ersek Date: Thu, 20 Feb 2014 22:54:45 +0100 Subject: OvmfPkg: increase max debug message length to 512 (RHEL only) Upstream prefers short debug messages (sometimes even limited to 80 characters), but any line length under 512 characters is just unsuitable for effective debugging. (For example, config strings in HII routing, logged by the platform driver "OvmfPkg/PlatformDxe" on DEBUG_VERBOSE level, can be several hundred characters long.) 512 is an empirically good value. --- OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c b/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c index 585f9fb..88f9e55 100644 --- a/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c +++ b/OvmfPkg/Library/PlatformDebugLibIoPort/DebugLib.c @@ -27,7 +27,7 @@ // // Define the maximum debug and assert message length that this library supports // -#define MAX_DEBUG_MESSAGE_LENGTH 0x100 +#define MAX_DEBUG_MESSAGE_LENGTH 0x200 /** This constructor function does not have to do anything. -- 1.8.3.1