WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] C-state/P-state spew fills xm dmesg buffers
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 10 Apr 2009 07:13:20 +0100
Cc:
Delivery-date: Thu, 09 Apr 2009 23:13:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <0A882F4D99BBF6449D58E61AAFD7EDD61036A612@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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
Thread-index: Acm5I0bEEu77EvM2SqqBGs9Sptc22gACWSA0ABHimUAAC88V7Q==
Thread-topic: [Xen-devel] C-state/P-state spew fills xm dmesg buffers
User-agent: Microsoft-Entourage/12.15.0.081119
No, but would be easy to add.

 K.

On 10/04/2009 01:36, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> Thanks for clearing it. BTW, is there plan to allow console ring
> buffer size configurable?
> 
> Thanks,
> Kevin 
> 
>> From: Keir Fraser
>> Sent: 2009年4月10日 0:03
>> 
>> Yeah, it's noisy. I'll quieten it.
>> 
>> -- Keir
>> 
>> On 09/04/2009 15:55, "Dan Magenheimer"
>> <dan.magenheimer@xxxxxxxxxx> wrote:
>> 
>>> 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
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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