Skip to content
Snippets Groups Projects
Commit 9253abbe authored by Glauber Costa's avatar Glauber Costa Committed by Pekka Enberg
Browse files

xen: silence messages


Xen boot is not totally silent. The devices usually print through
device_printf, which right now is hooked at printf. Changing that to debugf
already gets rid of most messages. However, netfront by itself manually prints
some messages with printf. They are changed as well.

Please note that the messages in netfront are changed directly to debug,
instead to device_printfs as well. This is because although we just hook that
to a printer, device_printf is supposed to prepend the messages with device
information.  We don't do it now, but could do it in the future. That is why
the original code used printf directly, and I am keeping that intent.

Reviewed-by: default avatarNadav Har'El <nyh@cloudius-systems.com>
Signed-off-by: default avatarGlauber Costa <glommer@cloudius-systems.com>
Signed-off-by: default avatarPekka Enberg <penberg@cloudius-systems.com>
parent f3fe2238
No related branches found
No related tags found
No related merge requests found
......@@ -200,7 +200,7 @@ static inline void disk_destroy(struct disk *dp)
{
}
#define device_printf(dev, ...) printf(__VA_ARGS__)
#define device_printf(dev, ...) debugf(__VA_ARGS__)
__BEGIN_DECLS
void device_set_ivars(device_t dev, void *ivars);
int device_get_children(device_t dev, device_t **devlistp, int *devcountp);
......
......@@ -2018,7 +2018,7 @@ xn_query_features(struct netfront_info *np)
np->maxfrags = 1;
if (val) {
np->maxfrags = MAX_TX_REQ_FRAGS;
printf(" feature-sg");
debug(" feature-sg");
}
if (xs_scanf(XST_NIL, xenbus_get_otherend_path(np->xbdev),
......@@ -2028,10 +2028,10 @@ xn_query_features(struct netfront_info *np)
np->xn_ifp->if_capabilities &= ~(IFCAP_TSO4|IFCAP_LRO);
if (val) {
np->xn_ifp->if_capabilities |= IFCAP_TSO4|IFCAP_LRO;
printf(" feature-gso-tcp4");
debug(" feature-gso-tcp4");
}
printf("\n");
debug("\n");
}
static int
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment