mirror of https://github.com/ipxe/ipxe.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 <mcb30@ipxe.org>pull/1193/merge
parent
5d64469a9e
commit
be5bf0aa7a
|
@ -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,
|
||||
|
|
Loading…
Reference in New Issue