Received: by 10.223.164.202 with SMTP id h10csp4691345wrb; Wed, 29 Nov 2017 10:14:22 -0800 (PST) X-Google-Smtp-Source: AGs4zMbhrELy7EDgq69sPr73Omge21JUt4zpzh2YcbXHFeb4TtTFaL/ap/W5Qx41jqnTJNmIPRzS X-Received: by 10.98.234.7 with SMTP id t7mr3857728pfh.88.1511979262433; Wed, 29 Nov 2017 10:14:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1511979262; cv=none; d=google.com; s=arc-20160816; b=keRMsdvYLxO5DIcJUSWLmfUiHrOQ/3e1pZ76TRH6BEEtKcfVrb4nZIjwTy1TMMjslo 4RKIngwUuidrtt+B4Um54LZyUK+A1CIc2hacHirCqadO9L+k5QQq8TDP4CKsOYa9Cg/J bHRqqZifHISTE4PiLZwJPFpjIwDQSmUaQqmIsJBj6vdkfXi0ebRlrc8bTDpqmai1w5xP sEb/QtPvr8uE4eO+OxX2wNWaaYhVpOPkPQVZ0DjUVApeor6MZu22zsLr6dAHPVNjGimH wBOhCYFEykWo8p4VBpVxGdog9nQiKpAoACgssQbUTI0AEF+jqaVGOvW1DMXBLrkFcRGg NxPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=nsXWTijf5cS2VigVWHLIDFELP5YtnYXbV6mWs72Bf8Q=; b=mKvCBLrNR0RjKIUeDSO4uh0HSQK+Ei1sIpgama9YRpERncbFe+yVwX02dQLoBliEfr y0pjyikRTCXAVFVdbcJrsvcbb3iJu3djCgmIIDJOCUrRknm0hJGMMMOJuhk6BLVJHbwW qh8C8lbR5XqgKF6/c7fWsLMREzS1pyRMG89a5lvmkvCsdDYC9JQ9Z6DccSiJDUW+aUrJ pBfMVT3+U3iIjQ3HECNdxgRkwpEAkV0etsNe8ZoFwxNt4JSJoKtCSjWeZsCuOEUbWEoZ 5CxBSLWazImRkv27BqH598m/wNW5F3Wy14WJNNoIeQPStJT6QRPkRm73fhZ7r+FtyEhM 6jWg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u86si1734878pfg.173.2017.11.29.10.14.12; Wed, 29 Nov 2017 10:14:22 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932581AbdK2MjY (ORCPT + 70 others); Wed, 29 Nov 2017 07:39:24 -0500 Received: from mga07.intel.com ([134.134.136.100]:25522 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932569AbdK2MjX (ORCPT ); Wed, 29 Nov 2017 07:39:23 -0500 Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Nov 2017 04:39:22 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,473,1505804400"; d="scan'208";a="1249872049" Received: from mylly.fi.intel.com (HELO [10.237.72.50]) ([10.237.72.50]) by fmsmga002.fm.intel.com with ESMTP; 29 Nov 2017 04:39:20 -0800 Subject: Re: [PATCH] x86/entry/64: Fix native_load_gs_index() SWAPGS handling with IRQ state tracing enabled To: Thomas Gleixner Cc: Ingo Molnar , linux-kernel , Andy Lutomirski , Peter Zijlstra , Linus Torvalds , Borislav Petkov References: <0fede9f9-88b0-a6e7-1027-dfb2019b8ef2@linux.intel.com> <20171129070951.hjjjpbyilzaak4ig@gmail.com> <17b6e0c8-db18-f63d-0118-52b85c0c2a7f@linux.intel.com> From: Jarkko Nikula Message-ID: Date: Wed, 29 Nov 2017 14:39:19 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/29/2017 11:28 AM, Thomas Gleixner wrote: > On Wed, 29 Nov 2017, Jarkko Nikula wrote: > >> On 11/29/2017 09:09 AM, Ingo Molnar wrote: >>> Hm, that commit looks broken with irq-tracing enabled. Does the >>> patch below fix it? >>> >> No, it makes the machine not to boot at all :-( >> >> Log below when I used my config (now attached). With x86_64_defconfig it >> booted twice but didn't survive suspend/resume. However several other boot >> attempts with x86_64_defconfig failed somewhat similarly. Not in the same >> place but hanging anyway. With my own config it seems to always end up failing >> in trace_hardirqs_off_caller. > > Does it work when you disable all the tracing muck? > My config seems to work with Ingo's patch if I disable both CONFIG_FTRACE and CONFIG_PROVE_LOCKING which disables the CONFIG_TRACE_IRQS_FLAGS. x86_64_defconfig with CONFIG_FTRACE disabled is still unstable. Sometimes hangs during bootup and sometimes boots up to userspace. -- Jarkko From 1585424303567257150@xxx Wed Nov 29 18:00:38 +0000 2017 X-GM-THRID: 1585383480543829622 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread