From: Michael Brown Date: Thu, 20 Mar 2025 14:30:34 +0000 (+0000) Subject: [efi] Show image address range in veto debug messages X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=be5bf0aa7a0d76d8426a04c88d1ec6e7c5293ff1;p=thirdparty%2Fipxe.git [efi] Show image address range in veto debug messages When hunting down a misbehaving OEM driver to add it to the veto list, it can be very useful to know the address ranges used by each driver. Add this information to the verbose debug messages. Signed-off-by: Michael Brown --- diff --git a/src/interface/efi/efi_veto.c b/src/interface/efi/efi_veto.c index 37aa9a379..1b2332041 100644 --- a/src/interface/efi/efi_veto.c +++ b/src/interface/efi/efi_veto.c @@ -569,9 +569,6 @@ static int efi_veto_find ( EFI_HANDLE driver, const char *manufacturer, EFI_STATUS efirc; int rc; - DBGC2 ( &efi_vetoes, "EFIVETO checking %s\n", - efi_handle_name ( driver ) ); - /* Mark as not vetoed */ memset ( veto, 0, sizeof ( *veto ) ); @@ -621,6 +618,9 @@ static int efi_veto_find ( EFI_HANDLE driver, const char *manufacturer, } /* Check vetoes */ + DBGC2 ( &efi_vetoes, "EFIVETO checking %s [%p,%p)\n", + efi_handle_name ( driver ), loaded.loaded->ImageBase, + ( loaded.loaded->ImageBase + loaded.loaded->ImageSize ) ); for ( i = 0 ; i < ( sizeof ( efi_vetoes ) / sizeof ( efi_vetoes[0] ) ) ; i++ ) { if ( efi_vetoes[i].veto ( binding.binding, loaded.loaded,