From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756036AbcCNUSj (ORCPT ); Mon, 14 Mar 2016 16:18:39 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:47579 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753187AbcCNUSh (ORCPT ); Mon, 14 Mar 2016 16:18:37 -0400 Date: Mon, 14 Mar 2016 21:18:26 +0100 From: Peter Zijlstra To: Andy Lutomirski Cc: Linus Torvalds , Paolo Bonzini , xen-devel , Arjan van de Ven , Borislav Petkov , X86 ML , Andrew Morton , KVM list , Andy Lutomirski , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v4 2/5] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops Message-ID: <20160314201826.GQ6344@twins.programming.kicks-ass.net> References: <20160314120202.GD15800@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 14, 2016 at 11:10:16AM -0700, Andy Lutomirski wrote: > A couple of the wrmsr users actually care about performance. These > are the ones involved in context switching and, to a lesser extent, in > switching in and out of guest mode. Right, this very much includes a number of perf MSRs. Some of those get called from the context switch path, others from the NMI handler.