; Oram, Isaac W ; Attar,
> AbdulLateef (Abdul Lateef)
> ; Tinh Nguyen
> Subject: Re: [edk2-devel] [PATCH] MdePkg: Add DEBUG_MANAGEABILITY print error
> level
>
> [AMD Official Use Only - General]
>
>
>
> > -Original Message-
> > From: devel@
; Igor
> Kulchytskyy ; Oram, Isaac W ;
> Attar, AbdulLateef (Abdul Lateef) ; Tinh
> Nguyen ; Kinney, Michael D
>
> Subject: Re: [edk2-devel] [PATCH] MdePkg: Add DEBUG_MANAGEABILITY
> print error level
>
> Caution: This message originated from an External Source. Use proper
Abner
> via groups.io
> Sent: Tuesday, April 18, 2023 7:06 PM
> To: Kinney, Michael D ; devel@edk2.groups.io
> Cc: Gao, Liming ; Liu, Zhiguang
> ; Nickle Wang ; Igor
> Kulchytskyy ; Oram, Isaac W ; Attar,
> AbdulLateef (Abdul Lateef)
> ; Tinh Nguyen
> Subject: Re:
[AMD Official Use Only - General]
I was hesitated having a new debug level for just RedfishPkg, until I realized
not only RedfishPkg but also ManageabilityPKg and edk2-redfish-client need a
specific debug level. The scope look to me big enough to create a new
individual debug level due to lot o
Do we really need a new debug level?
The DEBUG_INIT/WARN/INFO/VERBOSE levels can be enabled/disabled in individual
modules.
I imagine even within the set of manageability components you will want to use
those
different levels to adjust verbosity of the debug log.
Mike
> -Original Message-
From: Abner Chang
Bug #4414
Add DEBUG_MANAGEABILITY print error lever to
output debug message of detailed manageability
related module information, such as
- RedfishPkg:
- HTTP header/request/response
- JSON plain text
- Refish resource
- Redfish Host interface information
- Redfish cr
