From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops Date: Wed, 30 Sep 2015 15:10:02 +0200 Message-ID: <20150930131002.GK2881__42071.0098733709$1443618747$gmane$org@worktop.programming.kicks-ass.net> References: <130a3b7ef4788baae3a6fe71293ab17442bc9a0a.1442793572.git.luto@kernel.org> <20150921084642.GA30984@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Linus Torvalds Cc: Andrew Morton , KVM list , the arch/x86 maintainers , Linux Kernel Mailing List , xen-devel , Paolo Bonzini , Thomas Gleixner , Andy Lutomirski , Arjan van de Ven , Ingo Molnar List-Id: xen-devel@lists.xenproject.org On Mon, Sep 21, 2015 at 09:36:15AM -0700, Linus Torvalds wrote: > On Mon, Sep 21, 2015 at 1:46 AM, Ingo Molnar wrote: > > > > Linus, what's your preference? > > So quite frankly, is there any reason we don't just implement > native_read_msr() as just > > unsigned long long native_read_msr(unsigned int msr) > { > int err; > unsigned long long val; > > val = native_read_msr_safe(msr, &err); > WARN_ON_ONCE(err); > return val; > } > > Note: no inline, no nothing. Just put it in arch/x86/lib/msr.c, and be > done with it. I don't see the downside. > > How many msr reads are so critical that the function call > overhead would matter? Get rid of the inline version of the _safe() > thing too, and put that thing there too. There are a few in the perf code, and esp. on cores without a stack engine the call overhead is noticeable. Also note that the perf MSRs are generally optimized MSRs and less slow (we cannot say fast, they're still MSRs) than regular MSRs.