[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [Xen-users] Re: Xen 4 TSC problems
>>> On 23.10.12 at 17:34, Mauro <mrsanna1@xxxxxxxxx> wrote: > On 23 October 2012 16:46, Mauro <mrsanna1@xxxxxxxxx> wrote: >> On 23 October 2012 16:43, Jan Beulich <JBeulich@xxxxxxxx> wrote: >>>>>> On 23.10.12 at 16:07, Mauro <mrsanna1@xxxxxxxxx> wrote: >>>> Today I had another clock jump so cpuidle=0 doesn't work. >>>> I'll stay using clocksource= pit and cpuidle =0 for a while to see if >>>> they together work. >>>> But...how to know what C states the kernel uses? >>> >>> If "cpuidle=0" alone doesn't work, your problem is not C-state >>> related, and you don't need to look up how much of it the native >>> kernel uses. >> >> Ok, cpuidle=0 however is to be used because also clocksource=pit alone >> doesn't work. >> Now I'll use both params and see what happens. > > Sorry for the noise, I'm not sure if it has been really a clock jump. > Retry using only cpuidle=0 and then what Jan has suggested. > If you want to see the C states tell me how to do. Let's wait with that until you're settled on whether "cpuidle=0" alone works. Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |