From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753155Ab2LQQ5F (ORCPT ); Mon, 17 Dec 2012 11:57:05 -0500 Received: from terminus.zytor.com ([198.137.202.10]:48408 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751935Ab2LQQ5D (ORCPT ); Mon, 17 Dec 2012 11:57:03 -0500 Message-ID: <50CF4EBB.6060602@zytor.com> Date: Mon, 17 Dec 2012 08:56:27 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Yinghai Lu CC: Ingo Molnar , Bernd Schubert , linux-kernel@vger.kernel.org, Borislav Petkov , Suresh Siddha , Thomas Gleixner Subject: Re: [regression] 3.7 ends in APIC panic References: <50CB3EAB.309@itwm.fraunhofer.de> <50CE0C82.20708@itwm.fraunhofer.de> <50CEE586.10800@itwm.fraunhofer.de> <20121217140238.GA626@gmail.com> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/17/2012 08:53 AM, Yinghai Lu wrote: > On Mon, Dec 17, 2012 at 6:02 AM, Ingo Molnar wrote: >> >> I suspect this needs to be fixed/improved: currently it's way >> too easy to disable x2apic support accidentally. >> > > We can just enable x2apic by default when CONFIG_EMBEDDED is not set. > Yes, although we should expect to have to blacklist hosts more aggressively. Unfortunately we still don't have a good distinction between the ThinkPads that have broken BIOSes when x2apic is on and those that don't. -hpa