[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Fri, 10 Apr 2009 08:36:23 +0800
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc:
  • Delivery-date: Thu, 09 Apr 2009 17:38:23 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acm5I0bEEu77EvM2SqqBGs9Sptc22gACWSA0ABHimUA=
  • Thread-topic: [Xen-devel] C-state/P-state spew fills xm dmesg buffers

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.