)]}' { "log": [ { "commit": "f3f3149f35b9195ef4b761b1353fc0766b5f53be", "tree": "96e67c82e8ea6ce57ce5f83a8036f87a8d534867", "parents": [ "6ff10de374cc68ff2024247793176dc8a1b317ea" ], "author": { "name": "Alok Kataria", "email": "akataria@vmware.com", "time": "Mon Jun 23 18:21:56 2008 -0700" }, "committer": { "name": "Ingo Molnar", "email": "mingo@elte.hu", "time": "Tue Jun 24 13:53:46 2008 +0200" }, "message": "x86: use cpu_khz for loops_per_jiffy calculation, cleanup\n\nAs suggested by Ingo, remove all references to tsc from init/calibrate.c\n\nTSC is x86 specific, and using tsc in variable names in a generic file should\nbe avoided. lpj_tsc is now called lpj_fine, since it is related to fine tuning\nof lpj value. Also tsc_rate_* is called timer_rate_*\n\nSigned-off-by: Alok N Kataria \u003cakataria@vmware.com\u003e\nCc: Arjan van de Ven \u003carjan@infradead.org\u003e\nCc: Daniel Hecht \u003cdhecht@vmware.com\u003e\nCc: Tim Mann \u003cmann@vmware.com\u003e\nCc: Zach Amsden \u003czach@vmware.com\u003e\nCc: Sahil Rihan \u003csrihan@vmware.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n" }, { "commit": "3da757daf86e498872855f0b5e101f763ba79499", "tree": "bffffafed7322c66a1b886b661cfd8a8a7f5a924", "parents": [ "e01b70ef3eb3080fecc35e15f68cd274c0a48163" ], "author": { "name": "Alok Kataria", "email": "akataria@vmware.com", "time": "Fri Jun 20 15:06:33 2008 -0700" }, "committer": { "name": "Ingo Molnar", "email": "mingo@elte.hu", "time": "Mon Jun 23 22:51:33 2008 +0200" }, "message": "x86: use cpu_khz for loops_per_jiffy calculation\n\nOn the x86 platform we can use the value of tsc_khz computed during tsc\ncalibration to calculate the loops_per_jiffy value. Its very important\nto keep the error in lpj values to minimum as any error in that may\nresult in kernel panic in check_timer. In virtualization environment, On\na highly overloaded host the guest delay calibration may sometimes\nresult in errors beyond the ~50% that timer_irq_works can handle,\nresulting in the guest panicking.\n\nDoes some formating changes to lpj_setup code to now have a single\nprintk to print the bogomips value.\n\nWe do this only for the boot processor because the AP\u0027s can have\ndifferent base frequencies or the BIOS might boot a AP at a different\nfrequency.\n\nSigned-off-by: Alok N Kataria \u003cakataria@vmware.com\u003e\nCc: Arjan van de Ven \u003carjan@infradead.org\u003e\nCc: Daniel Hecht \u003cdhecht@vmware.com\u003e\nCc: Tim Mann \u003cmann@vmware.com\u003e\nCc: Zach Amsden \u003czach@vmware.com\u003e\nCc: Sahil Rihan \u003csrihan@vmware.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n" }, { "commit": "5cba6d22e35a05adb28fdea191b232501518c455", "tree": "65ebdb01d81cbe218cbdedc6e52f759a1b18cc0a", "parents": [ "daa49ff50a0cd1ddf88019e9afc41e26640ab1c4" ], "author": { "name": "Andrew Morton", "email": "akpm@linux-foundation.org", "time": "Tue Mar 04 14:28:45 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue Mar 04 16:35:12 2008 -0800" }, "message": "ndelay(): switch to C function to avoid 64-bit division\n\nWe should be able to do ndelay(some_u64), but that can cause a call to\n__divdi3() to be emitted because the ndelay() macros does a divide.\n\nFix it by switching to static inline which will force the u64 arg to be\ntreated as an unsigned long. udelay() takes an unsigned long arg.\n\n[bunk@kernel.org: reported m68k build breakage]\nCc: Adrian Bunk \u003cbunk@kernel.org\u003e\nCc: Evgeniy Polyakov \u003cjohnpol@2ka.mipt.ru\u003e\nCc: Martin Michlmayr \u003ctbm@cyrius.com\u003e\nCc: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nCc: Ralf Baechle \u003cralf@linux-mips.org\u003e\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\nCc: Adrian Bunk \u003cbunk@kernel.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "1e92a550e80fef01ebcc0bcd0896109cdb986c72", "tree": "6cdb7bc6c6ad51644f9b899b2604d26fe7cd540b", "parents": [ "ddf5f75a16b3e7460ffee881795aa168dffcd0cf" ], "author": { "name": "Anton Blanchard", "email": "anton@samba.org", "time": "Thu Jun 15 14:11:22 2006 +1000" }, "committer": { "name": "Paul Mackerras", "email": "paulus@samba.org", "time": "Wed Jun 21 15:01:33 2006 +1000" }, "message": "[POWERPC] Fix mdelay badness on shared processor partitions\n\nOn partitioned PPC64 systems where a partition is given 1/10 of a\nprocessor, we have seen mdelay() delaying for 10 times longer than it\nshould. The reason is that the generic mdelay(n) does n delays of 1\nmillisecond each. However, with 1/10 of a processor, we only get a\none-millisecond timeslice every 10ms. Thus each 1 millisecond delay\nloop ends up taking 10ms elapsed time.\n\nThe solution is just to use the PPC64 udelay function, which uses the\ntimebase to ensure that the delay is based on elapsed time rather than\nhow much processing time the partition has been given. (Yes, the\ngeneric mdelay uses the PPC64 udelay, but the problem is that the\nstart time gets reset every millisecond, and each time it gets reset\nwe lose another 9ms.)\n\nSigned-off-by: Anton Blanchard \u003canton@samba.org\u003e\nSigned-off-by: Paul Mackerras \u003cpaulus@samba.org\u003e\nAcked-by: Andrew Morton \u003cakpm@osdl.org\u003e\n" }, { "commit": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2", "tree": "0bba044c4ce775e45a88a51686b5d9f90697ea9d", "parents": [], "author": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "message": "Linux-2.6.12-rc2\n\nInitial git repository build. I\u0027m not bothering with the full history,\neven though we have it. We can create a separate \"historical\" git\narchive of that later if we want to, and in the meantime it\u0027s about\n3.2GB when imported into git - space that would just make the early\ngit days unnecessarily complicated, when we don\u0027t have a lot of good\ninfrastructure for it.\n\nLet it rip!\n" } ] }