From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932200AbbIUSgk (ORCPT ); Mon, 21 Sep 2015 14:36:40 -0400 Received: from mail.skyhub.de ([78.46.96.112]:50720 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752126AbbIUSgi (ORCPT ); Mon, 21 Sep 2015 14:36:38 -0400 Date: Mon, 21 Sep 2015 20:36:34 +0200 From: Borislav Petkov To: Andy Lutomirski Cc: Linus Torvalds , Ingo Molnar , Thomas Gleixner , Paolo Bonzini , xen-devel , Arjan van de Ven , Andrew Morton , KVM list , the arch/x86 maintainers , Linux Kernel Mailing List , Peter Zijlstra Subject: Re: [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops Message-ID: <20150921183634.GE3666@pd.tnic> References: <130a3b7ef4788baae3a6fe71293ab17442bc9a0a.1442793572.git.luto@kernel.org> <20150921084642.GA30984@gmail.com> 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 Mon, Sep 21, 2015 at 11:16:30AM -0700, Andy Lutomirski wrote: > In the interest of sanity, I want to drop the "native_", too, since > there appear to be few or no good use cases for native_read_msr as > such. I'm tempted to add new functions read_msr and write_msr that > forward to rdmsrl_safe and wrmsrl_safe. Just change the msr_read/msr_write() ones in arch/x86/lib/msr.c to take a u64 and you're there. > It looks like the msr helpers are every bit as bad as the TSC helpers > used to be :( Yap. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.