[v3,0/2] xen: some CONFIG_DEBUG_INFO changes

Message

Jürgen Groß April 5, 2023, 1:56 p.m. UTC

Enabling crash dump analysis of the hypervisor requires the hypervisor
having been built with CONFIG_DEBUG_INFO enabled. Today this requires
either CONFIG_DEBUG or CONFIG_EXPERT set, which are both not security
supported.

This small series changes that in order to allow security supported
Xen builds with the capability to do crash dump analysis via the
"crash" tool.

Note that due to problems with test machines proper support for EFI
booted systems hasn't been verified, so this will likely need some more
work.

Changes in V2:
- comments addressed

Changes in V3:
- comments addressed

Juergen Gross (2):
  xen: move CONFIG_DEBUG_INFO out of EXPERT section
  xen: update CONFIG_DEBUG_INFO help text

 xen/Kconfig.debug | 22 +++++++++++++++-------
 1 file changed, 15 insertions(+), 7 deletions(-)

Comments

Jan Beulich April 18, 2023, 6:14 a.m. UTC | #1

On 05.04.2023 15:56, Juergen Gross wrote:
> Enabling crash dump analysis of the hypervisor requires the hypervisor
> having been built with CONFIG_DEBUG_INFO enabled. Today this requires
> either CONFIG_DEBUG or CONFIG_EXPERT set, which are both not security
> supported.
> 
> This small series changes that in order to allow security supported
> Xen builds with the capability to do crash dump analysis via the
> "crash" tool.
> 
> Note that due to problems with test machines proper support for EFI
> booted systems hasn't been verified, so this will likely need some more
> work.
> 
> Changes in V2:
> - comments addressed
> 
> Changes in V3:
> - comments addressed
> 
> Juergen Gross (2):
>   xen: move CONFIG_DEBUG_INFO out of EXPERT section
>   xen: update CONFIG_DEBUG_INFO help text
> 
>  xen/Kconfig.debug | 22 +++++++++++++++-------
>  1 file changed, 15 insertions(+), 7 deletions(-)

Seeing no-one else showing any interest either way:
Acked-by: Jan Beulich <[e-mail]>

Jan