From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: Userspace MSR handling Date: Mon, 25 May 2009 13:29:48 +0200 Message-ID: <4A1A812C.60403@redhat.com> References: <9ae48b020905221311h1859d5a1v3653404721d5208b@mail.gmail.com> <790CB8FA-1660-4F6B-BEEC-AAB9724DDD64@suse.de> <4A193878.4030206@redhat.com> <4A1A7B14.5000205@redhat.com> <4A1A7F03.1020106@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Graf , Ed Swierk , "kvm@vger.kernel.org" To: Avi Kivity Return-path: Received: from mx2.redhat.com ([66.187.237.31]:59148 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750889AbZEYL3x (ORCPT ); Mon, 25 May 2009 07:29:53 -0400 In-Reply-To: <4A1A7F03.1020106@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 05/25/09 13:20, Avi Kivity wrote: > It should have been implemented as mmio. Maybe implement an ioctl that > converts rdmsr/wrmsr to equivalent mmios? > > struct kvm_msr_mmio { > __u32 msr; > __u32 nr; > __u64 mmio; > __u32 flags; > __u32 pad[3]; > } Funny way to tunnel msr access through the existing interface. Should work though I think. > In any case it should reject the standard msr ranges to prevent Alex > from implementing cpu emulation in userspace. ;) cheers, Gerd