From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: Should KVM_GUEST stop depending on PARAVIRT? Date: Mon, 27 Jul 2015 20:30:13 +0200 Message-ID: <55B678B5.8040602@redhat.com> References: <55B63933.4090702@redhat.com> <55B66F42.3000202@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: KVM list To: Andy Lutomirski Return-path: Received: from mx1.redhat.com ([209.132.183.28]:42400 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750923AbbG0SaS (ORCPT ); Mon, 27 Jul 2015 14:30:18 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 27/07/2015 19:51, Andy Lutomirski wrote: > > > I think I'm missing something. Does KVM_GUEST hook read_msr and > > > write_msr? I don't see it. > > > > PARAVIRT does, and it's the main reason why you'd want PARAVIRT for a > > KVM guest. > > Still confused. On a KVM guest (with PARAVIRT=y), doesn't read_msr do > exactly the same thing it does on native, albeit with more indirection > and patching involved? With PARAVIRT=y it never #GPs: .read_msr = native_read_msr_safe, .write_msr = native_write_msr_safe, I don't remember if it's this way on bare-metal too. Paolo