Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752083AbcDBPVe (ORCPT ); Sat, 2 Apr 2016 11:21:34 -0400 Received: from mail-ig0-f196.google.com ([209.85.213.196]:35232 "EHLO mail-ig0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751219AbcDBPVc (ORCPT ); Sat, 2 Apr 2016 11:21:32 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 2 Apr 2016 10:21:31 -0500 X-Google-Sender-Auth: ZqCR6QYLAC0VHuZhEyW5BAOlGO0 Message-ID: Subject: Re: [PATCH v5 0/9] Improve non-"safe" MSR access failure handling From: Linus Torvalds To: Andy Lutomirski Cc: Andy Lutomirski , X86 ML , Paolo Bonzini , Peter Zijlstra , KVM list , Arjan van de Ven , xen-devel , Linux Kernel Mailing List , Andrew Morton , Borislav Petkov Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 531 Lines: 15 On Sat, Apr 2, 2016 at 10:13 AM, Andy Lutomirski wrote: > > I also tried a bad wrmsrl at a couple early points. Very very early > it just works with not warning. A little later and it prints the > warning. Ok, that sounds like the correct behavior - I'm sure the very very early ones "warned" too, it just got dropped on the floor due to being before the printing/logging was up and running. And even then, it's obviously much better than having machines mysteriously just reboot. Thanks, Linus