[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] C-state/P-state spew fills xm dmesg buffers
I've noticed with xen-unstable on my quad-core x dual-thread (that's 8 processors to xen), the boot info spewed for all the C-state/P-state stuff quickly fills the xm dmesg buffer and I lose some of the early-in-boot lines. Do we really need to know "reg.{space_id,bit_width,bit_offset,access_size, address}" and all that other info? Even if so, is there a more compact way to print it? _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |