Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758363AbaGWXKg (ORCPT ); Wed, 23 Jul 2014 19:10:36 -0400 Received: from one.firstfloor.org ([193.170.194.197]:53870 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750706AbaGWXKf (ORCPT ); Wed, 23 Jul 2014 19:10:35 -0400 Date: Thu, 24 Jul 2014 01:10:32 +0200 From: Andi Kleen To: Andy Lutomirski Cc: Andi Kleen , "H. Peter Anvin" , Borislav Petkov , "linux-kernel@vger.kernel.org" , Linus Torvalds , X86 ML Subject: Re: STI architectural question (and lretq -- I'm not even kidding) Message-ID: <20140723231032.GZ18735@two.firstfloor.org> References: <8738drrcxp.fsf@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > I think that, other than broadcast MCEs, #MC that hits in kernel mode > is non-recoverable, or at least can't safely be recovered. (There's a > separate APIC interrupt for recoverable errors, I think, but that's a > much saner interface.) There are multiple valid cases where #MC can return. -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/