From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 0/3] x86/paravirt: Fix baremetal paravirt MSR ops Date: Thu, 17 Sep 2015 17:29:01 +0200 Message-ID: <55FADC3D.70202@redhat.com> References: <20150917071920.GA14296@gmail.com> <55FADBE6.9040008@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Andy Lutomirski , X86 ML , Peter Zijlstra , KVM list , xen-devel , "linux-kernel@vger.kernel.org" , Linus Torvalds , Thomas Gleixner , Peter Zijlstra , Andrew Morton , "H. Peter Anvin" To: Arjan van de Ven , Andy Lutomirski , Ingo Molnar Return-path: In-Reply-To: <55FADBE6.9040008@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 17/09/2015 17:27, Arjan van de Ven wrote: >> >>> ( We should double check that rdmsr()/wrmsr() results are never left >>> uninitialized, but are set to zero or so, for cases where the >>> return code is not >>> checked. ) >> >> It sure looks like native_read_msr_safe doesn't clear the output if >> the rdmsr fails. > > I'd suggest to return some poison not just 0... What about 0 + WARN? Paolo > less likely to get interesting surprises that are insane hard to > debug/diagnose