Subject : upstream regression (IO-APIC?) Submitter : Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> Date : 2008-10-30 0:00 References : http://marc.info/?l=linux-kernel&m=122532510328618&w=4 This entry is being used for tracking a regression from 2.6.27. Please don't close it until the problem is fixed in the mainline.
This apparently is a regression from 2.6.26. Caused by: commit 3da757daf86e498872855f0b5e101f763ba79499 Author: Alok Kataria <akataria@vmware.com> Date: Fri Jun 20 15:06:33 2008 -0700 x86: use cpu_khz for loops_per_jiffy calculation Signed-off-by: Alok N Kataria <akataria@vmware.com> Cc: Arjan van de Ven <arjan@infradead.org> Cc: Daniel Hecht <dhecht@vmware.com> Cc: Tim Mann <mann@vmware.com> Cc: Zach Amsden <zach@vmware.com> Cc: Sahil Rihan <srihan@vmware.com> Signed-off-by: Ingo Molnar <mingo@elte.hu> Patch : http://marc.info/?l=linux-kernel&m=122563711522315&w=4
(In reply to comment #1) > This apparently is a regression from 2.6.26. > > Caused by: > > commit 3da757daf86e498872855f0b5e101f763ba79499 > Author: Alok Kataria <akataria@vmware.com> > Date: Fri Jun 20 15:06:33 2008 -0700 > > x86: use cpu_khz for loops_per_jiffy calculation > This is not a kernel bug, looks like a qemu, timing emulator bug. http://lkml.org/lkml/2008/11/3/222 Bart mentions this on the thread, ================== I now noticed that the problem happens only with HZ == 250 host and HZ == 1000 guest. When host and guest are using the same HZ setting everything works fine. ================== Rafael, will leave upto you to decide if we should close this bug. Thanks, Alok
Let's close it, then.
Yep, closing it is fine with me. PS There is also some kind of workaround available with forcing CONFIG_HZ=250's lpj value using "lpj=" kernel option for CONFIG_HZ=1000 kernel.