- 29 Jul, 2005 33 commits
-
-
Ravikiran G Thirumalai authored
While booting with SMT disabled in bios, when using acpi srat to setup cpu_to_node[], sparse apic_ids create problems. Without this patch, intel x86_64 boxes with hyperthreading disabled in the bios (and which rely on srat for numa setup) endup having incorrect values in cpu_to_node[] arrays, causing sched domains to be built incorrectly etc. Signed-off-by:
Ravikiran Thirumalai <kiran@scalex86.org> Signed-off-by:
Shai Fultheim <shai@scalex86.org> Cc: Andi Kleen <ak@suse.de> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Andi Kleen authored
arch/x86_64/pci/k8-bus.c: In function `fill_mp_bus_to_cpumask': arch/x86_64/pci/k8-bus.c:32: warning: unused variable `printed' Signed-off-by:
Andi Kleen <ak@suse.de> Signed-off-by:
-
Nishanth Aravamudan authored
Replace schedule_timeout() with msleep() to guarantee the task delays as expected. Signed-off-by:
Nishanth Aravamudan <nacc@us.ibm.com> Signed-off-by:
Domen Puncer <domen@coderock.org> Signed-off-by:
-
Jesse Millan authored
This patch eliminates the GCC4 warning on the x86_64 platform: kernel/sched.c:1824: warning: control may reach end of non-void function 'sched_find_first_bit' being inlined. The change follows the lead of others, i.e. it is guaranteed that at least one of b[0], b[1], or b[2] will have a bit set and evaluate to true. That being said, GCC4.0.0 notices that the code flow does not return anything if b[0], b[1] and b[2] are not true. Since we know better, if it's not b[0] or b[1], it has to be b[2]. Signed-off-by:
Jesse Millan <jessem@cs.pdx.edu> Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
This avoids some potential stack overflows with very deep softirq callchains. i386 does this too. TOADD CFI annotation Signed-off-by:
-
Andi Kleen authored
Save a byte here and there. Ultimatively useless, but these things always catch my eyes when reading the code so just fix them for now. Also I got at least one patch fixing of them already, which gives a good excuse. Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
This avoids confusing the disassembler. Costs 2 bytes per BUG. Thanks to Suresh Siddha and Jan Beulich for suggesting suitable instructions. Signed-off-by:
-
Andreas Gruenbacher authored
Icecream preprocesses c sources locally, and sends the result off to a remote host for compiling. It does not recognize includes at assembler level. The fix is to put the assemberincludes an a separate .s file, which will always be assembled locally. Signed-off-by:
Andreas Gruenbacher <agruen@suse.de> Signed-off-by:
-
Andi Kleen authored
Use physical mode instead of logical mode to address more CPUs. This is also used in the CPU hotplug case to avoid a race. Signed-off-by:
-
Andi Kleen authored
Will be obsolete with physflat. Signed-off-by:
-
Andi Kleen authored
Not used anymore since quite some time. Just uses -m32 instead. Signed-off-by:
-
Andi Kleen authored
This patch will create machinecheck sysdev directories per CPU. All of the cpus still share the same ctl banks. When compiled with CONFIG_HOTPLUG_CPU, it will also bring up/down sysdev directories as cpus go up/down. I have tested the patch along with CONFIG_HOTPLUG_CPU option on in 2.6.13-rc1 kernel. Minor changes by AK: remove useless unload function Signed-off-by:
Jacob Shin <jacob.shin@amd.com> Signed-off-by:
-
Andi Kleen authored
From: Keith Manning Print a boot message for hotplug memory zones Signed-off-by:
-
Keith Mannthey authored
Signed-off-by:
-
Andi Kleen authored
Harmless because the kernel didn't use it. Noticed by Travis Betak Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
Were either outdated or misleading. Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
Minor cleanup. Move things into their include files, remove obsolete includes, fix indentation, remove obsolete special cases etc. I also added the per cpu section to asm-generic/sections.h and fixed init/main.c to use it. Signed-off-by:
-
Andi Kleen authored
No need to print kernel addresses there and clarify what the APIC-ID is. Signed-off-by:
-
Andi Kleen authored
Does not change any semantics because numa_add_cpu checks for CPU 0 anyways. Signed-off-by:
-
Andi Kleen authored
Various code needs this information now before the actual SMP bootup. Instead of computing it on the fly while booting the other CPUs set it up now while initial MPtable/MADT parsing. Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
Makes it slightly more efficient. Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Alexander Nyberg authored
When the x86_64 cpu hotplug changes went in it added a check in default_do_nmi() which kills NMI delivery on any CPU but the BSP. The NMI watchdog is brought up quite some time before the online bit is set in num_online_cpus so this won't work very well. The nmi watchdogs on cpus that are not BSP will never be reprogrammed and no NMIs. Why was this check added? How does an offlined cpu receive an NMI? Signed-off-by:
Alexander Nyberg <alexn@telia.com> Cc: Andi Kleen <ak@suse.de> Cc: Andrew Morton <akpm@osdl.org> Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk> Cc: <ashok.raj@intel.com> Signed-off-by:
-
- 28 Jul, 2005 7 commits
-
-
Linus Torvalds authored
-
Joachim Nilsson authored
I ran glade-2 on the glade file, fixed two missing stock icons and cleaned up the C code that inserts the single/split/full modes. The rest of the patch is minor cleanups only. I refrained from using all the included xpm icons in images.c (like qconf.cc does) in favour of using the stock Gtk+ icons instead. Oh, yes there was a "back" bug in split mode that I also removed, oh well... It has been tested with success by several people, including Jesper Juhl, Randy Dunlap and myself. Signed-off-by:
Sam Ravnborg <sam@ravnborg.org> Signed-off-by:
-
Linus Torvalds authored
It may shut up gcc, but it also incorrectly changes the semantics of the smp_call_function() helpers. You can fix the warning other ways if you are interested (create another inline function that takes no arguments and returns zero), but preferably gcc just shouldn't complain about unused return values from statement expressions in the first place.
-
Linus Torvalds authored
-
Steven Rostedt authored
Avoid using "rep scas", just let the compiler select a sequence of regular instructions. Signed-off-by:
Steven Rostedt <rostedt@goodmis.org> Signed-off-by:
-
Richard Henderson authored
Apparently gcc 4.0 complains about "({ 0; });", which leads to -Werror breakage in one of the alpha oprofile modules. One might could argue that this is a gcc bug, in that statement-expressions should be considered to be function-like rather than statement-like for the purposes of this warning. But it's just as easy to use an inline function in the first place, side-stepping the issue. Signed-off-by: -
Bjorn Helgaas authored
If the PCDP supplies parity, use it (only none/even/odd supported), and don't append parity/stop bit arguments unless baud is present. Signed-off-by:
Bjorn Helgaas <bjorn.helgaas@hp.com> Signed-off-by:
-
