Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4435425ybi; Mon, 3 Jun 2019 10:48:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqwb2SGkzfh2cv/IR5Y0QcEOA/t4arSe+526999DPPNBwsRCQjG2/tuSFgp0t4UFGgmL4kz1 X-Received: by 2002:a17:902:1021:: with SMTP id b30mr32113876pla.324.1559584100132; Mon, 03 Jun 2019 10:48:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559584100; cv=none; d=google.com; s=arc-20160816; b=ogypayyKQzq9k1fMiOUcP1lg0kCztwSz1cJA5KrpN4ioOKq90mgfgb/QcnR7CzhNq2 dlF0HgpOhKUt4rX+iMrUSP0dc3iw/Ur5e7m/0LqQltmckIAw20l4I+AfVLIQsp6u3Tzj /OscM3Z2cR7ftG6/B0D9xaH0CNyIGSXNIXInt73y7RHVUHJOgbLeW3lBdlLJrG/Kmg/o wQo0Fiurd523lDd3bihNDphJvKY9I7hTANZcKi8gg+DmYlwuSl5DoMaNF3Ogc7Zhj8JG 2Tl4HaxN7UoIdx1Z0SyucESXNrOLq6SNeDYr63QoyYk04ov7qMbbL9YySBdZbLJ857AH r+VA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=x2gJCl8W8rwMtWz1L4Cn/CBOi+oW9ZkczDnYr62ubRw=; b=k4s2NrBUHBRvoq7n3ti/7PngUxWzYxg74Yrig3dRNySlORtV0aShp63I7ZxLYbt5Ov gZRNDnLapMjukT5EOfPPPuZ2Ntrka0RhFmQHHK5cd7bCrhEaLAxAQQ1BbUOYsWQW/vXQ KHdJLncLqIj/1tjZ3Y29BkvlCPygpQXveFSn2lTRj2a6iMkIfUueNJniLhDoFXPhuAeF b6Xu3UCrIO9uLdsCb2zFOCGxznmgiyOjoblFTILzQoj4prMGNmBq4LDnBNpW9QpZqLJp aW71L6wOKaH8vGXAhP1gsuwGdUfar2ib7FjB9iN5SmWHrHQt8v9T6RANIDl6PPiQS9Il 848g== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x28si21349190pff.104.2019.06.03.10.48.04; Mon, 03 Jun 2019 10:48:20 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728710AbfFCQSS (ORCPT + 99 others); Mon, 3 Jun 2019 12:18:18 -0400 Received: from mga02.intel.com ([134.134.136.20]:31738 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726521AbfFCQSS (ORCPT ); Mon, 3 Jun 2019 12:18:18 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jun 2019 09:18:18 -0700 X-ExtLoop1: 1 Received: from sjchrist-coffee.jf.intel.com (HELO linux.intel.com) ([10.54.74.36]) by orsmga006.jf.intel.com with ESMTP; 03 Jun 2019 09:18:17 -0700 Date: Mon, 3 Jun 2019 09:18:17 -0700 From: Sean Christopherson To: Jiri Kosina Cc: Andy Lutomirski , Andy Lutomirski , "Rafael J. Wysocki" , Josh Poimboeuf , "Rafael J. Wysocki" , Thomas Gleixner , the arch/x86 maintainers , Pavel Machek , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , Peter Zijlstra , Linux PM , Linux Kernel Mailing List Subject: Re: [PATCH v4] x86/power: Fix 'nosmt' vs. hibernation triple fault during resume Message-ID: <20190603161817.GD13384@linux.intel.com> References: <5564116.e9OFvgDRbB@kreacher> <98E57C7E-24E2-4EB8-A14E-FCA80316F812@amacapital.net> <20190603142330.GA13384@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 03, 2019 at 05:24:26PM +0200, Jiri Kosina wrote: > On Mon, 3 Jun 2019, Sean Christopherson wrote: > > > For P6 and later, i.e. all modern CPUs, Intel processors go straight to > > halted state and don't fetch/decode the HLT instruction. > > That'd be a rather relieving fact actually. Do you happen to know if this > is stated in some Intel documentation and we've just overlooked it, or > whether it's rather an information that's being carried over from > generation to generation by whispering through grapevine? I highly doubt it's officially stated anywhere. Intel's approach to this type of micro-architecture specific behavior is (usually) to word the SDM in such a way that both approaches are legal. E.g. a 1993 version of the SDM says "Returns to interrupted HLT instruction", whereas in 1995, which just so happens to coincide with the introduction of the P6 architecture, the SDM started saying "Returns to HALT state" and added the blurb about "will generate a memory access to fetch the HLT instruction (if it is not in the internal cache)" so that the old behavior is still legal. All that being said, the "straight to HALT" behavior is now the de facto standard since lots of people will yell loudly if it changes.