From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753464AbbANSr0 (ORCPT ); Wed, 14 Jan 2015 13:47:26 -0500 Received: from mail.skyhub.de ([78.46.96.112]:47297 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752108AbbANSrZ (ORCPT ); Wed, 14 Jan 2015 13:47:25 -0500 Date: Wed, 14 Jan 2015 19:47:14 +0100 From: Borislav Petkov To: Andy Lutomirski Cc: Matt Fleming , LKML , "linux-efi@vger.kernel.org" , "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , Peter Zijlstra Subject: Re: EFI mixed mode + perf = rampant triple faults Message-ID: <20150114184714.GD6902@pd.tnic> References: <5491B4A8.905@amacapital.net> <20141231183739.GA28946@console-pimps.org> <20150114165151.GA3479@codeblueprint.co.uk> <20150114183546.GC6902@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 14, 2015 at 10:38:25AM -0800, Andy Lutomirski wrote: > That's not a real MCE, though -- it happens synchronously instead of MCE can be synchronous in a sense too, as a result of executing an insn, for example, i.e., EIPV bit set. > at MCE priority with all the associated messiness. Or is the idea to > just stick that in after switching to the 32-bit mode being tested? Yes, the idea was to simply trigger a real exception after switching to 32-bit while still with 64-bit IDT handlers. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --