From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops Date: Tue, 22 Sep 2015 10:12:36 +0200 Message-ID: <56010D74.9020808@redhat.com> References: <130a3b7ef4788baae3a6fe71293ab17442bc9a0a.1442793572.git.luto@kernel.org> <20150921084642.GA30984@gmail.com> <56003506.1050100@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Linus Torvalds , Ingo Molnar , Thomas Gleixner , xen-devel , Andrew Morton , KVM list , the arch/x86 maintainers , Linux Kernel Mailing List , Peter Zijlstra To: Andy Lutomirski , Arjan van de Ven Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 21/09/2015 19:43, Andy Lutomirski wrote: > And maybe the KVM user return notifier. No, not really. If anything, the place in KVM where it makes a difference is vmx_save_host_state, which is also only using always-present MSRs. But don't care about KVM. First clean it up, then we can add back inline versions like __rdmsr or rdmsr_fault or rdmsr_unsafe or whatever. Paolo