Re: [Xen-devel] [PATCH v1] xen/mce: Don't spam the console with "CPUx: Temperature z" (v2)

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Wed, Jun 04, 2014 at 03:49:52PM +0100, Jan Beulich wrote:
> >>> On 04.06.14 at 15:37, <konrad.wilk@xxxxxxxxxx> wrote:
> > If the machine has been quite busy it ends up with these
> > messages printed on the hypervisor console:
> > 
> > (XEN) CPU3: Temperature/speed normal
> > (XEN) CPU1: Temperature/speed normal
> > (XEN) CPU0: Temperature/speed normal
> > (XEN) CPU1: Temperature/speed normal
> > (XEN) CPU0: Temperature/speed normal
> > (XEN) CPU2: Temperature/speed normal
> > (XEN) CPU3: Temperature/speed normal
> > (XEN) CPU0: Temperature/speed normal
> > (XEN) CPU2: Temperature/speed normal
> > (XEN) CPU3: Temperature/speed normal
> > (XEN) CPU1: Temperature/speed normal
> > (XEN) CPU0: Temperature above threshold
> > (XEN) CPU0: Running in modulated clock mode
> > (XEN) CPU1: Temperature/speed normal
> > (XEN) CPU2: Temperature/speed normal
> > (XEN) CPU3: Temperature/speed normal
> > 
> > While the state changes are important, the non-altered
> > state information is not needed. As such add a latch
> > mechanism to only print the information if it has
> > changed since the last update.
> 
> But isn't the interrupt supposed to happen only when state changes
> in the first place?


HA!
That is what I thought too, but this machine keeps on triggering
this interrupt.
> 
> Jan
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel