This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] C-state/P-state spew fills xm dmesg buffers

To: "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] C-state/P-state spew fills xm dmesg buffers
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Thu, 9 Apr 2009 07:55:06 -0700 (PDT)
Delivery-date: Thu, 09 Apr 2009 07:55:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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

<Prev in Thread] Current Thread [Next in Thread>