From 6324a2a8ae4fc96c9e13d39483c5ee0cb1fff619 Mon Sep 17 00:00:00 2001

Message-Id: <6324a2a8ae4fc96c9e13d39483c5ee0cb1fff619.1534970217.git.crobinso@redhat.com>

In-Reply-To: <37942481c89eca732239c23fe606680e6e3faf77.1534970217.git.crobinso@redhat.com>

References: <37942481c89eca732239c23fe606680e6e3faf77.1534970217.git.crobinso@redhat.com>

From: Laszlo Ersek <lersek@redhat.com>

Date: Thu, 20 Feb 2014 22:54:45 +0100

Subject: [PATCH 04/17] OvmfPkg: increase max debug message length to 512

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.

Signed-off-by: Laszlo Ersek <lersek@redhat.com>

Signed-off-by: Cole Robinson <crobinso@redhat.com>

---

 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 36cde54976..c0c4eaee0f 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

 /**

   Prints a debug message to the debug output device if the specified error level is enabled.

-- 

2.17.1