commit 67644726317a8274be4a3d0ef85b9ccebaa90304 tree c2bcf873d19d1b18d65e4f5d6d5c3cd613e9cb13 parent 66004a6ca23f2a2408b32cbe27fda0389fb8f9dc author Dave Jones Sun, 02 Apr 2006 23:34:19 -0700 committer Linus Torvalds Sun, 09 Apr 2006 12:35:53 -0700 [SELINUX] Fix build after ipsec decap state changes. security/selinux/xfrm.c: In function 'selinux_socket_getpeer_dgram': security/selinux/xfrm.c:284: error: 'struct sec_path' has no member named 'x' security/selinux/xfrm.c: In function 'selinux_xfrm_sock_rcv_skb': security/selinux/xfrm.c:317: error: 'struct sec_path' has no member named 'x' Signed-off-by: Dave Jones Signed-off-by: David S. Miller Signed-off-by: Linus Torvalds commit 66004a6ca23f2a2408b32cbe27fda0389fb8f9dc tree 7f11359eec8c511e5fcf7340c93f9a84a2bad0e2 parent b8feb47f992d314c956add15c1118430120635bb author Linus Torvalds Sun, 09 Apr 2006 12:14:02 -0700 committer Linus Torvalds Sun, 09 Apr 2006 12:14:02 -0700 Move request_standard_resources() back to before PCI probing This effectively undoes the PCI resource allocation changes done in commit b408cbc704352eccee301e1103b23203ba1c3a0e, but leaves the cleanups of that commit in place. We're going back to marking the resources reported by e820 busy _before_ doing PCI probing, so that any PCI resource that clashes with the BIOS- reported memory map will be reloacted to a non-clashing area. The reason? Larry Finger reports that his laptop has the cardbus controller set up by the BIOS so that it conflicts with the e820 memory map, and needs to be relocated. See http://bugzilla.kernel.org/show_bug.cgi?id=6337 for more details. We'll have to work out how to handle the fbcon problem that caused that commit in the first place in some other way. Cc: Ivan Kokshaysky Cc: Greg Kroah-Hartman Cc: Antonino A. Daplas Cc: Tested-by: Larry Finger Signed-off-by: Linus Torvalds commit b8feb47f992d314c956add15c1118430120635bb tree fa134a28d0696edbe76bb3191ac00969440c7398 parent 67d53ea5a3d42aadeb1584e757ca4660c0e8a810 author Andi Kleen Fri, 07 Apr 2006 19:50:34 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:53 -0700 [PATCH] x86_64: Update 32-bit system call table Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 67d53ea5a3d42aadeb1584e757ca4660c0e8a810 tree 054906bb672c6faad287ede5b34c53d56afdc629 parent bbd3aff89d4b34ef17a748e4c001ecc5b43e3e55 author Andi Kleen Fri, 07 Apr 2006 19:50:31 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:53 -0700 [PATCH] x86_64: Eliminate IA32_NR_syscalls define Or rather compute it based on the table length automatically. This also has the intended side effect of not warning for new system calls anymore. Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit bbd3aff89d4b34ef17a748e4c001ecc5b43e3e55 tree 26e9521b03e9cff515a96774cf3ac67c9b612bce parent 97c2803c9c694cafbd9f5e43a25903e0abf25188 author Sam Ravnborg Fri, 07 Apr 2006 19:50:28 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:53 -0700 [PATCH] x86_64: fix CONFIG_REORDER Fix CONFIG_REORDER. The value of cflags-y was assined to CFLAGS before cflags-y was assigned the value used for CONFIG_REORDER. Use cflags-y for all CFLAGS options in the Makefile to avoid this happening again. Signed-off-by: Sam Ravnborg Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 97c2803c9c694cafbd9f5e43a25903e0abf25188 tree e70f35adaae6c95cf5e4557a92ccaa3f827ae2d3 parent e48c4729d23a026f3711d5e36add5cce894b4913 author John Blackwood Fri, 07 Apr 2006 19:50:25 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:53 -0700 [PATCH] x86_64: Plug GS leak in arch_prctl() In linux-2.6.16, we have noticed a problem where the gs base value returned from an arch_prtcl(ARCH_GET_GS, ...) call will be incorrect if: - the current/calling task has NOT set its own gs base yet to a non-zero value, - some other task that ran on the same processor previously set their own gs base to a non-zero value. In this situation, the ARCH_GET_GS code will read and return the MSR_KERNEL_GS_BASE msr register. However, since the __switch_to() code does NOT load/zero the MSR_KERNEL_GS_BASE register when the task that is switched IN has a zero next->gs value, the caller of arch_prctl(ARCH_GET_GS, ...) will get back the value of some previous tasks's gs base value instead of 0. Change the arch_prctl() ARCH_GET_GS code to only read and return the MSR_KERNEL_GS_BASE msr register if the 'gs' register of the calling task is non-zero. Side note: Since in addition to using arch_prctl(ARCH_SET_GS, ...), a task can also setup a gs base value by using modify_ldt() and write an index value into 'gs' from user space, the patch below reads 'gs' instead of using thread.gs, since in the modify_ldt() case, the thread.gs value will be 0, and incorrect value would be returned (the task->thread.gs value). When the user has not set its own gs base value and the 'gs' register is zero, then the MSR_KERNEL_GS_BASE register will not be read and a value of zero will be returned by reading and returning 'task->thread.gs'. The first patch shown below is an attempt at implementing this approach. Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit e48c4729d23a026f3711d5e36add5cce894b4913 tree 9f5556934bcba4d5ced8f06d0215a7534b3a8bbc parent b20367a6c2a0cd937cb1f0a8cf848f1402fef99c author Andi Kleen Fri, 07 Apr 2006 19:50:21 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:53 -0700 [PATCH] i386: Remove printk about reboot fixups at reboot Printk doesn't have any value Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit b20367a6c2a0cd937cb1f0a8cf848f1402fef99c tree 8624096baed40f8f89e757b2d170a7b4d1844575 parent 49c93e84d8b2d602a07c302c7e3cd4fa09095fbb author Jordan Hargrave Fri, 07 Apr 2006 19:50:18 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:53 -0700 [PATCH] x86_64: Fix drift with HPET timer enabled If the HPET timer is enabled, the clock can drift by ~3 seconds a day. This is due to the HPET timer not being initialized with the correct setting (still using PIT count). If HZ changes, this drift can become even more pronounced. HPET patch initializes tick_nsec with correct tick_nsec settings for HPET timer. Vojtech comments: "It's not entirely correct (it assumes the HPET ticks totally exactly), but it's significantly better than assuming the PIT error there." Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 49c93e84d8b2d602a07c302c7e3cd4fa09095fbb tree a59d0bb7a9f1df9f3187e466e3937ea9ffd83343 parent 8c30b1a74aed4041f183e183a149b7dfbdc6c20e author Andi Kleen Fri, 07 Apr 2006 19:50:15 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:52 -0700 [PATCH] i386/x86-64: Return defined error value for bad PCI config space accesses Mostly to get better handling when a extended config space access has to fallback to Type1. Cc: gregkh@suse.de Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 8c30b1a74aed4041f183e183a149b7dfbdc6c20e tree 1476500ffdefa842c632e960196fefdadb04ca04 parent e405d067298b2b960bf20318e91ed842157c65bc author Andi Kleen Fri, 07 Apr 2006 19:50:12 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:52 -0700 [PATCH] i386/x86_64: Check if MCFG works for the first 16 busses Previously only the first bus would be checked against Type 1. Why 16? Checking all would need too much memory and we can assume that systems with more than 16 busses have better than average quality BIOS. This is an additional defense against bad MCFG tables. Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit e405d067298b2b960bf20318e91ed842157c65bc tree edb9bf3a90c70e7b7d490504f7ea695b39aa6a08 parent 3d34ee6891e274dfb6a22930546d37738cdbe9c4 author Ravikiran G Thirumalai Fri, 07 Apr 2006 19:50:09 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:52 -0700 [PATCH] x86_64: Fixup read_mostly section on internode cache line size for vSMP Fixup the read mostly section to start at internode cacheline boundary. Signed-off-by: Ravikiran Thirumalai Signed-off-by: Shai Fultheim Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 3d34ee6891e274dfb6a22930546d37738cdbe9c4 tree 46b5ea716446d598bfb5680af05aac4aed5c6284 parent ac04dcaf6f567307fbeef9c3c1fff35280e53f02 author Andi Kleen Fri, 07 Apr 2006 19:50:06 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:52 -0700 [PATCH] x86_64: Don't return error for HPET initialization in initcall Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit ac04dcaf6f567307fbeef9c3c1fff35280e53f02 tree 0af1ec91c2cfda958e2320aa4030df5c312c91e4 parent 7bf36bbc5e0c09271f9efe22162f8cc3f8ebd3d2 author Andi Kleen Fri, 07 Apr 2006 19:50:03 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:52 -0700 [PATCH] x86_64: Don't export strlen twice Fix WARNING: vmlinux: 'strlen' exported twice. Previous export was in vmlinux Reported by Mats Johannesson Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 7bf36bbc5e0c09271f9efe22162f8cc3f8ebd3d2 tree 9e97e2f5774824f0e2fbff1d4e7c49e9938285f5 parent 553f265fe883a23502ee351845f09334790f18b8 author Andi Kleen Fri, 07 Apr 2006 19:50:00 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:52 -0700 [PATCH] x86_64: When user could have changed RIP always force IRET Intel EM64T CPUs handle uncanonical return addresses differently from AMD CPUs. The exception is reported in the SYSRET, not the next instruction. This leads to the kernel exception handler running on the user stack with the wrong GS because the kernel didn't expect exceptions on this instruction. This version of the patch has the teething problems that plagued an earlier version fixed. This is CVE-2006-0744 Thanks to Ernie Petrides and Asit B. Mallick for analysis and initial patches. Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 553f265fe883a23502ee351845f09334790f18b8 tree 1fd60e72d7d5cbed34812eb6763899d2bd37c152 parent be56db6186999a8571ae480cf2b929578f6dfd68 author Andi Kleen Fri, 07 Apr 2006 19:49:57 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:52 -0700 [PATCH] x86_64: Don't run NMI watchdog during machine checks Machine checks can stall the machine for a long time and it's not good to trigger the nmi watchdog during that. Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit be56db6186999a8571ae480cf2b929578f6dfd68 tree df0760d15a76b9615c02f37ad5941fd5b52c5658 parent 4211a30349e8d2b724cfb4ce2584604f5e59c299 author Dave Hansen Fri, 07 Apr 2006 19:49:54 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:51 -0700 [PATCH] x86_64: extra NODES_SHIFT definition The generic linux/numa.h file defines NODES_SHIFT to 0 in case the architecture did not. Every architecture which has a NUMA config option defines NODES_SHIFT in its asm-$ARCH headers, but only if NUMA is enabled, except for x86_64. This should make it like all the rest. Signed-off-by: Dave Hansen Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 4211a30349e8d2b724cfb4ce2584604f5e59c299 tree 59fdb0b812156bbff2266cc51b22d9d608898ecf parent d7fa706ce2c29cb751c15ca00f3aa7b223e3c9f0 author Jacob Shin Fri, 07 Apr 2006 19:49:51 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:51 -0700 [PATCH] x86_64: Proper null pointer check in powernow_k8_get This prevents crashes on dual core system when enough ticks are lost. Replaces earlier patch by me. Cc: Dave Jones Signed-off-by: Thomas Renninger Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit d7fa706ce2c29cb751c15ca00f3aa7b223e3c9f0 tree 0e19431741ca192c8c98d6f06edc56e0d4be08db parent 95d769aaf47abfc77b600631403ff5af6c990cff author Andi Kleen Fri, 07 Apr 2006 19:49:48 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:51 -0700 [PATCH] x86_64: Revert earlier powernow-k8 change Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 95d769aaf47abfc77b600631403ff5af6c990cff tree 738fff854613a086e7c1ad04074fa596b8554760 parent d1530d82e02fd96d4634a6d6f6538c8b778c43af author Andi Kleen Fri, 07 Apr 2006 19:49:45 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:51 -0700 [PATCH] i386: Consolidate modern APIC handling AMD systems have a modern APIC that supports 8 bit IDs, but don't have a XAPIC version number. Add a new "modern_apic" subfunction that handles this correctly and use it (nearly) everywhere where XAPIC is tested for. I removed one wart: the code specified that external APICs would use an 8bit APIC ID. But I checked a real 82093 data sheet and it says clearly that they only use 4bit. So I removed this special case since it would a bit awkward to implement now. I removed the valid APIC tests in mptable parsing completely. On any modern system they only check against the full field width (8bit) anyways and are no-ops. This also fixes them doing the wrong thing on >8 core Opterons. This makes i386 boot again on 16 core Opterons. Cc: Ingo Molnar Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit d1530d82e02fd96d4634a6d6f6538c8b778c43af tree f825ae536b1ee15208b0917de54e42e528b59be6 parent d3b6a349d233aecf2c52f7f4c150ca09f684f2d8 author Andi Kleen Fri, 07 Apr 2006 19:49:42 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:51 -0700 [PATCH] x86_64: Clear APIC feature bit when local APIC is disabled Needed for other checks later in ACPI. Pointed out by Len Brown Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit d3b6a349d233aecf2c52f7f4c150ca09f684f2d8 tree 3ab86b3ffc1dbe2eaa69c5bb041644975df60da7 parent ec0f08eeea6ac1d8c925f47e3677e4c985fd8f63 author Andi Kleen Fri, 07 Apr 2006 19:49:39 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:51 -0700 [PATCH] x86-64/i386: Don't process APICs/IO-APICs in ACPI when APIC is disabled. When nolapic was passed or the local APIC was disabled for another reason ACPI would still parse the IO-APICs until these were explicitely disabled with noapic. Usually this resulted in a non booting configuration unless "nolapic noapic" was used. I also disabled the local APIC parsing in this case, although that's only cosmetic (suppresses a few printks) This hopefully makes nolapic work in all cases. Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit ec0f08eeea6ac1d8c925f47e3677e4c985fd8f63 tree 053ede4e6c6648dc8d927a2ad17ef5e03069b3a2 parent fa47dd0ba303599f8adf8d8336ed2fb74efc47c5 author Andi Kleen Fri, 07 Apr 2006 19:49:36 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:51 -0700 [PATCH] x86_64: Don't sanity check Type 1 PCI bus access on newer systems Horus systems don't have anything on bus 0 which makes the Type 1 sanity checks fail. Use the DMI BIOS year to check for newer systems and always assume Type 1 works on them. I used 2001 as an pretty arbitary cutoff year. Cc: gregkh@suse.de Cc: Navin Boppuri Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit fa47dd0ba303599f8adf8d8336ed2fb74efc47c5 tree 5aad31f503964dafb047f15bf327e99e5ddbd5c7 parent 946f2ee5c7312e8acac4f3ab6629e7e2d36a3646 author Andi Kleen Fri, 07 Apr 2006 19:49:33 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:51 -0700 [PATCH] x86_64: Fix compilation with CONFIG_PCI=n / allnoconfig Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 946f2ee5c7312e8acac4f3ab6629e7e2d36a3646 tree 0821a2f3f59a089b73d33f64f59331460e20355a parent 952223683ec989e86328c24808fdb962c4dbeb0a author Arjan van de Ven Fri, 07 Apr 2006 19:49:30 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:51 -0700 [PATCH] i386/x86-64: Check that MCFG points to an e820 reserved area This patch introduces a user for the e820_all_mapped function: There have been several machines that don't have a working MMCONFIG, often because of a buggy MCFG table in the ACPI bios. This patch adds a simple sanity check that detects a whole bunch of these cases, and when it detects it, linux now boots rather than crash-and-burns. The accuracy of this detection can in principle be improved if there was a "is this entire range in e820 with THIS attribute", but no such function exist and the complexity needed for this is not really worth it; this simple check already catches most cases anyway. Signed-off-by: Arjan van de Ven Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 952223683ec989e86328c24808fdb962c4dbeb0a tree 0c7473d4469cba883bf880bbaa04900960806742 parent eee5a9fa63c97366cdea6ab3aa2ed9e3601812d0 author Arjan van de Ven Fri, 07 Apr 2006 19:49:27 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:50 -0700 [PATCH] x86_64: Introduce e820_all_mapped Introduce a e820_all_mapped() function which checks if the entire range is mapped with type. This is done by moving the local start variable to the end of each known-good region; if at the end of the function the start address is still before end, there must be a part that's not of the correct type; otherwise it's a good region. Signed-off-by: Arjan van de Ven Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit eee5a9fa63c97366cdea6ab3aa2ed9e3601812d0 tree b01876c5417f52173e9ab3d76c124df2042c9f62 parent a8062231d80239cf3405982858c02aea21a6066a author Arjan van de Ven Fri, 07 Apr 2006 19:49:24 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:17 -0700 [PATCH] x86_64: Rename e820_mapped to e820_any_mapped Rename e820_mapped to e820_any_mapped since it tests if any part of the range is mapped according to the type. Later steps will introduce e820_all_mapped which will check if the entire range is mapped with the type. Both have their merit. Signed-off-by: Arjan van de Ven Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit a8062231d80239cf3405982858c02aea21a6066a tree 0576493fa99cda91069fe3b67c19bd024858e69e parent 68a3a7feb08f960095072f28ec20f7900793c506 author Andi Kleen Fri, 07 Apr 2006 19:49:21 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:16 -0700 [PATCH] x86_64: Handle empty PXMs that only contain hotplug memory The node setup code would try to allocate the node metadata in the node itself, but that fails if there is no memory in there. This can happen with memory hotplug when the hotplug area defines an so far empty node. Now use bootmem to try to allocate the mem_map in other nodes. And if it fails don't panic, but just ignore the node. To make this work I added a new __alloc_bootmem_nopanic function that does what its name implies. TBD should try to use nearby nodes here. Currently we just use any. It's hard to do it better because bootmem doesn't have proper fallback lists yet. Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 68a3a7feb08f960095072f28ec20f7900793c506 tree 1d458822fd4414997b6f12ad8a915f785d7e730f parent 9d99aaa31f5994d1923c3713ce9144c4c42332e1 author Andi Kleen Fri, 07 Apr 2006 19:49:18 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:16 -0700 [PATCH] x86_64: Reserve SRAT hotadd memory on x86-64 From: Keith Mannthey, Andi Kleen Implement memory hotadd without sparsemem. The memory in the SRAT hotadd area is just preserved instead and can be activated later. There are a few restrictions: - Only one continuous hotadd area allowed per node The main problem is dealing with the many buggy SRAT tables that are out there. The strategy here is to reject anything suspicious. Originally from Keith Mannthey, with several hacks and changes by AK and also contributions from Andrew Morton [ TBD: Problems pointed out by KAMEZAWA Hiroyuki : 1) Goto's rebuild_zonelist patch will not work if CONFIG_MEMORY_HOTPLUG=n. Rebuilding zonelist is necessary when the system has just memory < 4G at boot, and hot add memory > 4G. because x86_64 has DMA32, ZONE_NORAML is not included into zonelist at boot time if system doesn't have memory >4G at boot. [AK: should just force the higher zones at boot time when SRAT tells us] 2) zone and node's spanned_pages and present_pages are not incremented. They should be. For example, our server (ia64/Fujitsu PrimeQuest) can equip memory from 4G to 1T(maybe 2T in future), and SRAT will *always* say we have possible 1T +memory. (Microsoft requires "write all possible memory in SRAT") When we reserve memmap for possible 1T memory, Linux will not work well in +minimum 4G configuraion ;) [AK: needs limiting to 5-10% of max memory] ] Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 9d99aaa31f5994d1923c3713ce9144c4c42332e1 tree ae608593ca196dd6493cccbdfc1b8dd098e91ee8 parent 805e8c03c9ea9bdb402a36341e02ec24825d5417 author Andi Kleen Fri, 07 Apr 2006 19:49:15 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:16 -0700 [PATCH] x86_64: Support memory hotadd without sparsemem Memory hotadd doesn't need SPARSEMEM, but can be handled by just preallocating mem_maps. This only needs some untangling of ifdefs to enable the necessary code even without SPARSEMEM. Originally from Keith Mannthey, hacked by AK. Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 805e8c03c9ea9bdb402a36341e02ec24825d5417 tree c7047d0e3b2e72a7885bfce80369c25c89936821 parent 903fcc608e9f531749024172277dc2fd15d5a587 author Andi Kleen Fri, 07 Apr 2006 19:49:12 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:16 -0700 [PATCH] x86_64: Clean up execve path Just call IRET always, no need for any special cases. Needed for the next bug fix. Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds commit 903fcc608e9f531749024172277dc2fd15d5a587 tree 6844416b377a7f4f7aaf29eb53ed140afa47699e parent 6246b6128bbe34d0752f119cf7c5111c85fe481d author Andi Kleen Fri, 07 Apr 2006 19:49:09 +0200 committer Linus Torvalds Sun, 09 Apr 2006 11:53:16 -0700 [PATCH] x86_64: Update defconfig Signed-off-by: Andi Kleen Signed-off-by: Linus Torvalds