From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932417AbcDDQXt (ORCPT ); Mon, 4 Apr 2016 12:23:49 -0400 Received: from mail.skyhub.de ([78.46.96.112]:39228 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756039AbcDDQXr (ORCPT ); Mon, 4 Apr 2016 12:23:47 -0400 Date: Mon, 4 Apr 2016 18:23:38 +0200 From: Borislav Petkov To: Andy Lutomirski Cc: X86 ML , Paolo Bonzini , Peter Zijlstra , KVM list , Arjan van de Ven , xen-devel , linux-kernel@vger.kernel.org, Linus Torvalds , Andrew Morton Subject: Re: [PATCH v5 0/9] Improve non-"safe" MSR access failure handling Message-ID: <20160404162338.GI351@pd.tnic> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Apr 02, 2016 at 07:01:31AM -0700, Andy Lutomirski wrote: > There are two parts here: > > ***** FIRST PART: EARLY EXCEPTIONS ***** > > The first few patches move some early panic code into C, add pt_regs > to early exception handling, and make fancy exception handlers work early. > > ***** SECOND PART: MSRs ***** > > Setting CONFIG_PARAVIRT=y has an unintended side effect: it silently > turns all rdmsr and wrmsr operations into the safe variants without > any checks that the operations actually succeed. ... FWIW: Reviewed-by: Borislav Petkov Definitely a step in the right direction, regardless of how we're going to be doing early_printk(), which is a tangential topic. This pile could be taken for a spin in tip. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.