virPCIVPDResourceGetKeywordPrefix: Fix logging

Use VIR_DEBUG instead of VIR_INFO as that's more appropriate and report
relevant information for debugging.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
This commit is contained in:
Peter Krempa 2024-01-24 15:13:16 +01:00
parent 810a3ca980
commit ab3f4d1b0b

View File

@ -61,20 +61,20 @@ virPCIVPDResourceGetKeywordPrefix(const char *keyword)
g_autofree char *key = NULL;
/* Keywords must have a length of 2 bytes. */
if (strlen(keyword) != 2) {
VIR_INFO("The keyword length is not 2 bytes: %s", keyword);
return NULL;
} else if (!(virPCIVPDResourceIsUpperOrNumber(keyword[0]) &&
virPCIVPDResourceIsUpperOrNumber(keyword[1]))) {
VIR_INFO("The keyword is not comprised only of uppercase ASCII letters or digits");
return NULL;
}
if (strlen(keyword) != 2 ||
!(virPCIVPDResourceIsUpperOrNumber(keyword[0]) &&
virPCIVPDResourceIsUpperOrNumber(keyword[1])))
goto cleanup;
/* Special-case the system-specific keywords since they share the "Y" prefix with "YA". */
if (virPCIVPDResourceIsSystemKeyword(keyword) || virPCIVPDResourceIsVendorKeyword(keyword))
key = g_strndup(keyword, 1);
else
key = g_strndup(keyword, 2);
cleanup:
VIR_DEBUG("keyword='%s' key='%s'", keyword, NULLSTR(key));
return g_steal_pointer(&key);
}