|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-changelog] [xen master] timer-op: demote a debugging message to really be debugging only
commit e134a69f5c649290accfe2d5e905c5810425b4c4
Author: Jan Beulich <jbeulich@xxxxxxxx>
AuthorDate: Tue Nov 3 18:11:15 2015 +0100
Commit: Jan Beulich <jbeulich@xxxxxxxx>
CommitDate: Tue Nov 3 18:11:15 2015 +0100
timer-op: demote a debugging message to really be debugging only
The issue the message points out may have been of relevance during the
early days, but shouldn't anymore.
Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
---
xen/common/schedule.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/xen/common/schedule.c b/xen/common/schedule.c
index c5f640f..292e9a0 100644
--- a/xen/common/schedule.c
+++ b/xen/common/schedule.c
@@ -1118,8 +1118,8 @@ long do_set_timer_op(s_time_t timeout)
* timeout in this case can burn a lot of CPU. We therefore go for a
* reasonable middleground of triggering a timer event in 100ms.
*/
- gprintk(XENLOG_INFO, "Warning: huge timeout set: %"PRIx64"\n",
- (uint64_t)timeout);
+ gdprintk(XENLOG_INFO, "Warning: huge timeout set: %"PRIx64"\n",
+ timeout);
set_timer(&v->singleshot_timer, NOW() + MILLISECS(100));
}
else
--
generated by git-patchbot for /home/xen/git/xen.git#master
_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |