[tesla-dev] [powertop bug] too many blank lines between processor state and event report

[Rafael Vanoni]

Li, Aubrey wrote:
> Rafael Vanoni wrote:
> 
>> Here's a patch for this one, basically raising the event report
>> according to the number of P/C states.
>>
>> Let me know what you think.
>>
> 
> moving subwindows is not a good idea, it caused segment fault sometimes
> on my side. "man mvwin" told me moving subwindows is allowed, but should
> be avoided.
> 
> we may setup window after we get ncstates and npstates, so that we can
> dynamically position the event report window based on the numbers.
> 
> Does it make sense?

Hmm.. yes, I looked into getting the number of cstates before, but 
that's happening after we've already created the windows. The kstat 
implementation you wrote is not in Nevada, so there's no way of getting 
that information without changing a good deal of code.

I'll have another go at it :)

BTW, would it be interesting to integrate the kstat c-state info into 
nevada ?

thanks
Rafael